Did you keep your optical drive or move your stock drive there?I put an 850 Evo in my late 2011 15" MBP and the only thing I noticed was a feeling of, "why didn't I do this sooner?"
Why now? As already mentioned, hard drives are not user replaceable anymore.
What is the plan behind this move?
The "man" documentation for the trimforce command indicates it was introduced in OS X 10.10.4, which remains in developer testing, but forum member mikeboss has determined it is not present in the current developer build.
Why now? As already mentioned, hard drives are not user replaceable anymore.
What is the plan behind this move?
+1 about HFS+. This is good news about 3rd party TRIM support and yeh, they are certainly doing it this way to make it clear that they are not responsible for how well this is going to work. But as you say, data loss due to data corruption (which is inevitable overtime btw) is entirely on Apple. I am surprised this doesn't get mentioned more often but I personally experienced it on a number of occasions. Files randomly become unusable for no apparent reason. It doesn't happen every day or on big scale but it does happen. and with HFS+ not doing any error checking corrupted files propagate to any kind of backups you have. This is the part that sucks the most and HFS+ is to blame here.Ha! Apple sure isn't liable for data loss using trim but don't worry, they've got you covered with their crappy HFS+ filesystem regardless of trim or 3rd party drives.
+1 about HFS+. This is good news about 3rd party TRIM support and yeh, they are certainly doing it this way to make it clear that they are not responsible for how well this is going to work. But as you say, data loss due to data corruption (which is inevitable overtime btw) is entirely on Apple. I am surprised this doesn't get mentioned more often but I personally experienced it on a number of occasions. Files randomly become unusable for no apparent reason. It doesn't happen every day or on big scale but it does happen. and with HFS+ not doing any error checking corrupted files propagate to any kind of backups you have. This is the part that sucks the most and HFS+ is to blame here.
Trim and garbage collection are technologies that work well together. They are not mutually exclusive. Without TRIM, the garbage collector is far less efficient. TRIM is the only way for the SSD to know which blocks are free. Garbage collection does not do this. SSDs store data in what's knows as "clusters". These are essentially groups of blocks of data. The SSD cannot free individual blocks, just entire clusters. Garbage collection compacts data into as few clusters as possible, so that it can clean up the empty blocks. Garbage collection has no way of knowing which blocks are empty without the OS telling it. If it doesn't know, it ends up moving around free blocks, thinking there's still important data in them. You need TRIM on any SSD, even SandForce, to get the best performance out of it.Most SSD manufacturers have garbage collection built into their controllers that cleans up during idle time. Those that stress their SSDs with lots of read/write will find more value in the Trim Enabler.
True words. People hear "garbage collector" and jump to conclusions about its purpose. There is no reputable source that has ever claimed garbage collection does what TRIM does, even if it's often repeated on the internet.Garbage collection works better if you have TRIM enabled as well.
https://www.cindori.org/trim-vs-garbage-collection/
TLDNR: Without TRIM, the drive doesn't 'know' that data has been deleted until the system gets around to trying to re-use that space. Garbage collection will still work without TRIM , but will waste time preserving and consolidating data that has actually been 'deleted'.
Also note that - at least with some types of garbage collection - you must take steps to ensure that it gets idle time to run (especially if its the system drive in a laptop that gets powered down when idle to save juice). See: http://forum.crucial.com/t5/Crucial-SSDs/My-SSD-used-to-be-so-much-faster-What-happened/ta-p/118310
OS X drivers do not support TRIM, if you have a 3rd party SSDs in the MacBook Pro and MacBook Air. Apple uses probably standard PCIe connectors in the future, which means lower costs for the consumer and for Apple.Why now? As already mentioned, hard drives are not user replaceable anymore.
What is the plan behind this move?
From:
http://arstechnica.com/gadgets/2015...e-interface-that-will-speed-up-your-next-ssd/
“Intel's new Broadwell CPUs and their chipsets include native support for M.2 and PCI Express boot drivers—neither PCIe-connected storage (hi Apple) nor the M.2 connector itself are new, but beginning with Broadwell systems each of those two things will become much more common.”
Sucks for TRIM Enabler. As someone that saw millions lost due to Apple adding features from software we sold, I know how it can hurt. On the other hand it is great to have functionality built-into the OS.
Has anyone in real life shown that trim actually makes a difference in a non-server system?
Hopefully I wont offend anyone - Apple has jerked us way too long with this issue and I am not thankful that they got around to something that should have come months and months ago. Apple may do some brilliant things but they also are getting notorious for abandoning some things, getting to others late and if we are to pay an Apple Tax, at least do us the courtesy and take care of the obvious in a timely fashion. Quite amazing how Apple has become the new Microsoft with jerking users around.
obscure formatting option?! far less efficient? what in the world are you talking about? I am talking about HFS+ which is the only file system I use. Its deficiencies with regards to data integrity are well-known and I am hardly the first person to point them out. yeh, I am by no means an expert on file systems but I know that some modern ones like ZFS do perform error checking on access. It's high time Apple developed a replacement for HFS+ that would do that too. At the very least that would prevent corrupted data from being silently copied over backups which is what HFS+ does. and I couldn't give less of a damn that some huge group of developers think it's ok for my data to get corrupt overtime with no effective way to stop it.You obviously have little experience really dealing with various formats. If HFS+ is a problem, you don't have it too bad. But please tell us about your obscure formatting option or one that is far less efficient and why you know better than a huge team of developers.
Finally!
Anyone talking about an Apple Tax... I just can't take them seriously. Not that I or anyone else will be offended, but like, I worry you might not even know you're a troll.
I mean, either you're buying Apple because you think it's the best, in which case it's worth every penny, or you're a poser buying Apple to look cool. The former acknowledges trade offs and has faith in Apple's proven successes while the latter is just grumpy they aren't using Windows and running around complaining about Apple Tax, planned obsolescence, or other conspiracies du jour.
obscure formatting option?! far less efficient? what in the world are you talking about? I am talking about HFS+ which is the only file system I use. Its deficiencies with regards to data integrity are well-known and I am hardly the first person to point them out. yeh, I am by no means an expert on file systems but I know that some modern ones like ZFS do perform error checking on access. It's high time Apple developed a replacement for HFS+ that would do that too. At the very least that would prevent corrupted data from being silently copied over backups which is what HFS+ does. and I couldn't give less of a damn that some huge group of developers think it's ok for my data to get corrupt overtime with no effective way to stop it.
Long overdue.
Maybe now they can fix the green button problem by making it maximize to full available screen while still showing the dock and file menu.