Depending on how you use the file, you *MAY* improve response time by
having the logicals (indexes) on the SSD and the data on spinning disks.
The system uses indexes a *LOT*, but you probably don't touch very much
of the data at any one time. If the system can grab the pointers to the
record you want from the index on SSD and then make only one arm swing
to get the data, you'll have pretty good response. Very likely that data
track will be cached as you will have accessed a record from it just a
few microseconds earlier so no head swing at all.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of darren@xxxxxxxxx
Sent: Tuesday, July 27, 2010 11:36 AM
To: midrange-l
Subject: Physicals or Logicals or both on an SSD
We currently have all data files in a certain library assigned to SSD
(IBM's Solid State Drive). The library is an MRP solution called BPCS.
I'm not up on the science of how logicals are managed, and my question
is, is there an advantage to having both logicals and physicals on the
SSD.
I've found that they can be separate, so that one or the other may be
assigned to standard HDD's. The SSD's are of limited size compared to
our regular HDD storage, and I'm considering whether performance
wouldn't be too badly impacted if I moved one of these object types off
of the drive.
I don't see a lot of discussion in technical documents on the use of
SSD's, so I'm hoping maybe someone here has some ideas.
Thank you in advance.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
