Not sure what I thnk might happen, but it is OK to use TRIM Enabler on a SSD that is setup as a Fusion Drive with a 1 TB HDD right? I'm just thinking because the Fusion drive moves blocks around and TRIM moves blocks around I don't want to mess things up.
Finally got round to doing mine on Wednesday. Apart from what i thought were crap tools from OWC (luckily i had my own) everything went fine and all is now up and running.
The first thing i done after installing everything was enable Trim. All seems to be working ok except smart only shows hours and power cycle count for SSD and temp,power and cycle for HDD.
As there seems to be nothing at the moment that tells me its doing any harm i'll leave it running for now.
Anyone find that it is worth it to enable trim on a new diy fusion drive in a 2012 mini?
If so are you using trim enabler to do it or something else?
I see there is an option to enable trim in Mountain lion tweaks, under the Lion tab.
Just wondering if its really needed and maybe it's better to just leave it off.
Thanks
I believe you should enable TRIM always, SSDs are dum in respect to HDDs. What i mean is that SSDs don't know which and where blocks are free or used, only way is to enable TRIM. It will guarantee good performance in time, otherwise after some time SSDs will slow down and degrade performance.
Just use TRIM enabler, it works fine.
This is not because SSDs are dumb. Spinning disks do not know which blocks are free or used either - this is why you have a file system 🙄
Have there been any tests between a system with trim enabled and one without trim enabled to show what kind of a benefit trim gives? If anyone has a pointer to that...
SSDs are actually dum as compared to HDDs. During write/delete operations they accumulate all sorts of garbage, becoming slower and slower. HDDs keep track of every single sector on their platters and keep a map of them, since they have access to the file system structures, including the list of unused clusters. SSDs don't have access to the file system structures. The quote below is not from me but from Wikipedia
(http://en.wikipedia.org/wiki/TRIM):
"In computing, a TRIM command allows an operating system to inform a solid-state drive (SSD) which blocks of data are no longer considered in use and can be wiped internally. While TRIM is frequently spelled in capital letters, it is a command name, not an acronym.
TRIM was introduced soon after SSDs started to become an affordable alternative to traditional hard disks. Because low-level operation of SSDs differs significantly from hard drives, the typical way in which operating systems handle operations like deletes and formats (not explicitly communicating the involved sectors/pages to the underlying storage medium) resulted in unanticipated progressive performance degradation of write operations on SSDs. TRIM enables the SSD to handle garbage collection overhead, which would otherwise significantly slow down future write operations to the involved blocks, in advance."
SSDs are actually dum as compared to HDDs. During write/delete operations they accumulate all sorts of garbage, becoming slower and slower. HDDs keep track of every single sector on their platters and keep a map of them, since they have access to the file system structures, including the list of unused clusters. SSDs don't have access to the file system structures. The quote below is not from me but from Wikipedia
(http://en.wikipedia.org/wiki/TRIM):
"In computing, a TRIM command allows an operating system to inform a solid-state drive (SSD) which blocks of data are no longer considered in use and can be wiped internally. While TRIM is frequently spelled in capital letters, it is a command name, not an acronym.
TRIM was introduced soon after SSDs started to become an affordable alternative to traditional hard disks. Because low-level operation of SSDs differs significantly from hard drives, the typical way in which operating systems handle operations like deletes and formats (not explicitly communicating the involved sectors/pages to the underlying storage medium) resulted in unanticipated progressive performance degradation of write operations on SSDs. TRIM enables the SSD to handle garbage collection overhead, which would otherwise significantly slow down future write operations to the involved blocks, in advance."
The difference in behaviour is due to the technology, as outlined by Giuly.
Correct.
So what did i write so wrong?
Aren't we stating the same thing but with different words/explanation?
SSDs are actually dum as compared to HDDs. During write/delete operations they accumulate all sorts of garbage, becoming slower and slower. HDDs keep track of every single sector on their platters and keep a map of them, since they have access to the file system structures, including the list of unused clusters. SSDs don't have access to the file system structures. The quote below is not from me but from Wikipedia
(http://en.wikipedia.org/wiki/TRIM):
TRIM is not recommended (may even degrade performance or cause issues) on Sandforce controllers.
Many SSDs do their own garbage collection and TRIM is simply not beneficial. Do some research on yours!
Perhaps an analogy is when people accidentally run 2 Windows programs that do the same system tasks like virus protection, etc. That causes all sorts of problems.
This bit:
They don't "accumulate garbage", they are slowed because an overwrite of a non-empty block requires an extra "erase" step before writing. This is in contrast to a HDD which just overwrites the block straight off.
TRIM informs the disk about unused blocks, yes, but this is not because SSDs are dumb and HDDs are smart.
EDIT: My previous response was a bit unfair, apologies.
A non empty block can be defined as a block partially occupied by garbage?
If SSDs need to be informed about unused blocks makes them less "wise" than HDDs., that's what i meant in saying that SSD's are dumb in respect to HDDs.
Thanks for the apologies, no need for them.