Saturday, November 13
If you run an 80GB Intel X25-M at its rated 4KB random-write performance, it will exceed its rated 4KB random-write endurance after just 3 days.
For a 32GB Intel X25-E, it would take about 28 months.
This is why the E-series runs five times the cost per gigabyte of the M-series.
What the real-world lifespan is for either drive range I have no idea, but I aim to find out.
Update: Based on the actual activity patterns on our server, the 80GB M-series would last 2½ years, and the 32-GB E-series (which is what we are using, 3 drives in a RAID-5 array) would last about three centuries.
Posted by: Steven Den Beste at Tuesday, November 16 2010 05:38 AM (+rSRq)
Posted by: J Greely at Tuesday, November 16 2010 06:19 AM (fpXGN)
Posted by: Steven Den Beste at Tuesday, November 16 2010 09:11 AM (+rSRq)
Posted by: Pete Zaitcev at Tuesday, November 16 2010 12:03 PM (9KseV)
Posted by: Pixy Misa at Tuesday, November 16 2010 02:58 PM (PiXy!)
Posted by: Pixy Misa at Tuesday, November 16 2010 03:02 PM (PiXy!)
What I was assuming was that if the same location was written a million times, the chips would be dead. Sounds like that's a huge overestimate. If it's only 10,000 the unit wouldn't last three hours.
Presumably this is something they'd have noticed during design and testing, so presumably they've got an answer -- most likely, as mentioned above, tuning Windows so it doesn't do that kind of thing.
Posted by: Steven Den Beste at Tuesday, November 16 2010 04:25 PM (+rSRq)
Posted by: Steven Den Beste at Tuesday, November 16 2010 04:26 PM (+rSRq)
Since there's almost no seek time on an SSD (there's a small delay to switch pages) for most uses you hardly notice this. A badly fragmented drive might only deliver 100MB/s on sequential reads instead of 200MB/s, and that's where TRIM comes in. Regular software defragmentation just gets remapped by the drive anyway and achieves nothing, so they had to add a drive command to do it directly.
Posted by: Pixy Misa at Wednesday, November 17 2010 01:48 AM (PiXy!)
Which gave me a really lousy time in December 2008 when I was trying to do a database reload and ran out of free blocks for the wear-leveling algorithm and the drive's performance plunged by 95% and I thought it was broken and had to get a replacement part shipped to Seattle on Christmas day at midnight in a blizzard.
Posted by: Pixy Misa at Wednesday, November 17 2010 01:52 AM (PiXy!)
Posted by: devizakereskedés at Saturday, December 04 2010 02:36 AM (EIzjX)
51 queries taking 0.1093 seconds, 261 records returned.
Powered by Minx 1.1.6c-pink.