On Fri, 10 Oct 2008, Marion Hakanson wrote: > > Yes, this advice was unexpected to me. Slicing up a spinning disk drive > is going to cause lots of extra seeks, but I'm having a hard time imagining > that an SSD is going to even notice that it's been sliced up.
>From what I have read, for most SSDs, if an already written part of an SSD needs to be re-written, the previously existing part needs to be read into the SSD's cache, 512K of the SSD is erased, the SSD cache is updated to reflect the updated bits, and then the 512K is restored. This could be a consideration if there may be multiple overlapping write requests. The SSD itself does not know about partitioning and in fact tries to distribute the write load as evenly as possible as part of the wear leveling algorithm. Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
