Comments on: Crisitunity: SSD for the MacBook http://www.neufeld.newton.ks.us/electronics/?p=1319 Sun, 08 Dec 2024 17:19:24 -0600 hourly 1 http://wordpress.org/?v=3.1.3 By: cyrozap http://www.neufeld.newton.ks.us/electronics/?p=1319&cpage=1#comment-27628 cyrozap Wed, 13 Apr 2011 03:27:58 +0000 http://www.neufeld.newton.ks.us/electronics/?p=1319#comment-27628 Remember to enable TRIM, lest your SSD performance decrease with time! http://osxdaily.com/2011/03/27/enable-trim-ssd-mac-os-x-10-6-7/ Remember to enable TRIM, lest your SSD performance decrease with time! http://osxdaily.com/2011/03/27/enable-trim-ssd-mac-os-x-10-6-7/

]]> By: robert http://www.neufeld.newton.ks.us/electronics/?p=1319&cpage=1#comment-27624 robert Tue, 12 Apr 2011 20:27:38 +0000 http://www.neufeld.newton.ks.us/electronics/?p=1319#comment-27624 At least on linux it seems necessary to align the partition/filesystem as such that the logical blocks match with the rather large write/read/erase blocks used in the SSD. The same is true for the new TB class disks that don't use 512B sectors, but 4k ones. If you have your system write e.g. 3 of its 'blocks' and the end of that doesn't align with the blocks on the disk, you'll have a read/modify/write operation because of the 'overshoot'. Also if the blocks don't line up the the large (128k or so) erase blocks of the SSD, it may happen that the device can't free a chunk, because of just a few bits overhanging from a previous block. I don't know if it's clear what I'm trying to say ;-) I've read that if you don't do it (I didn't with my SSD), the thing will get slower after time. At least on linux it seems necessary to align the partition/filesystem as such that the logical blocks match with the rather large write/read/erase blocks used in the SSD. The same is true for the new TB class disks that don’t use 512B sectors, but 4k ones. If you have your system write e.g. 3 of its ‘blocks’ and the end of that doesn’t align with the blocks on the disk, you’ll have a read/modify/write operation because of the ‘overshoot’.

Also if the blocks don’t line up the the large (128k or so) erase blocks of the SSD, it may happen that the device can’t free a chunk, because of just a few bits overhanging from a previous block.

I don’t know if it’s clear what I’m trying to say ;-)

I’ve read that if you don’t do it (I didn’t with my SSD), the thing will get slower after time.

]]> By: Keith Neufeld http://www.neufeld.newton.ks.us/electronics/?p=1319&cpage=1#comment-27623 Keith Neufeld Tue, 12 Apr 2011 19:56:31 +0000 http://www.neufeld.newton.ks.us/electronics/?p=1319#comment-27623 Robert, assuming you're referring to the new SSD, I didn't do anything special. The OS X installer creates (as far as I can tell) a single disk partition consuming the entire drive; I just let it do its thing. I did run a single-pass zeroing of the new drive before installing. Say more about what you have in mind? Robert, assuming you’re referring to the new SSD, I didn’t do anything special. The OS X installer creates (as far as I can tell) a single disk partition consuming the entire drive; I just let it do its thing.

I did run a single-pass zeroing of the new drive before installing.

Say more about what you have in mind?

]]> By: robert http://www.neufeld.newton.ks.us/electronics/?p=1319&cpage=1#comment-27622 robert Tue, 12 Apr 2011 19:35:19 +0000 http://www.neufeld.newton.ks.us/electronics/?p=1319#comment-27622 Did you do any erase block alignment of the partitions/filesystems, or is that taken care of by the mac os installer? Did you do any erase block alignment of the partitions/filesystems, or is that taken care of by the mac os installer?

]]>