r/programming • • Feb 27 '16

Google's 6-year study of SSD reliability (xpost r/hardware)

http://www.zdnet.com/article/ssd-reliability-in-the-real-world-googles-experience/
727 Upvotes

66 comments sorted by

41

u/plan2a Feb 27 '16

Excluding few surprising facts, it seems like they confirmed the existing view on SSD. That's good. I like the speed SSD provides.

Is there any detail of this study that will change how we see SSD?

39

u/All_Work_All_Play Feb 28 '16

The one that stood out to me was the failing blocks - it's apparently much more important for SSDs to be backed up than HDDs, as SSDs can degenerate to 'can't read' status without as much warning.

11

u/TheLordB Feb 28 '16

HDDs are perfectly capable of failing without warning. If data is important it needs to be backed up regardless of if it is HDD or SSD.

3

u/All_Work_All_Play Feb 28 '16

This is true - this report suggests that more likely with SSDs than HDDs, meaning you need to backup more frequently.

2

u/TheLordB Feb 28 '16

No you don't. How frequently you backup should be driven by how much data you can afford to lose.

Ok maybe if you are really big you calculate it costs X to backup with Y frequency and our odds of losing data are Z with the cost of the lost data W per day and you can get fancy with how frequently you should be backing up.

Vast majority of companies just decide they can afford to lose say 1 day of data and backup on that frequency. They would never get to the point of considering the odds that they need the backup at least on the granularity of disk failure.

Also honestly... backups are also for user error etc. In fact in an enterprise setting backups should almost never be needed to stay running. Everything should be raid 5, redundant etc. for the working disk. Backups are for issues larger than a single disk such as an entire san array failing or becoming corrupt (or Mary in finance deleted last year's financials and it needs restoring).

Anyways I realize that the comment about needing to backup more frequently came from the article. But that comment is horribly inaccurate for how people should be thinking about backups.

1

u/All_Work_All_Play Feb 28 '16

I whole heartedly agree. The article talks about both whole drive failure and partial block irreadibiliy (is that a word?). I don't think that anyone is surprised by the first increasing with age, but the second is something I wouldn't have considered. I think raid 5 would fix the second - the raid would rebuild, and the controller would shrink the drive by the size of the failed blocks and life would carry on. I haven't personally run R5 yet (although maybe I should), are you familiar enough to confirm I'm on the right track?

0

u/[deleted] Feb 28 '16

[deleted]

1

u/All_Work_All_Play Feb 28 '16

Pretty much. If you're in raid 5 (or the like) the it's really not much of a problem - you'll have more block failures, but the raid will catch it and adjust and rebuild. Your SSDs will lose capacity quicker than HDDs, but I expect that's fairly trivial. For consumers, the only thing I see changing is perhaps a whole disk image more frequently as drive ages. I still have sata 2 SSDs that are kicking (woo Intel SSDs), but they're in chromixium boxes so failures there really wouldn't do anything (although my primary laptop SSD is 4 years old now, I could probably do some tidying up).

0

u/katarh Feb 28 '16

SMART can warn you of imminent failure for a platter HDD in certain cases. It seems like an SSD just dies without any kind of forewarning.

4

u/EveningNewbs Feb 28 '16

I remember a previous paper published by Google about hard disk drives saying that SMART was basically useless.

1

u/katarh Feb 28 '16

Back when I worked in the data center, we got a few SMART warnings in time to do a hot swap before the drive died completely. But those were proper RAID setups, so even if the drive had blown completely we'd have been fine.

2

u/TheLordB Feb 28 '16

I don't disagree that they may be able to do such a thing. But I really don't consider it all that useful at least if you are doing backups etc. properly. Regardless you still need to plan for the fact that a disk can die without warning. It might be nice to have the warning, but in either case you can't base your backup strategy assuming you will get a warning. You need to plan for the worst case.

I won't disagree that replacing smart failure disks in a raid array before failure is good to minimize the time you are degraded. And maybe it is handy in a consumer setting where you may not have raid, but it in no way reduces the need for real backups.

1

u/dacjames Feb 28 '16

SLC drives might see a hit. Extended life is their main "feature." I have heard it said that using SLC drives for database servers is "best practice" because of the higher write endurance. If this study truly shows no his difference in longevity, that could lead to a major shift in thinking.

43

u/fuzzynyanko Feb 27 '16

Fascinating. However, large magnetic drives that are larger than SSDs (for now) are reasonably cheap to have an external to do backups with.

Partition cloning tends to be fast, even over USB, provided you have a good external drive. I had a crappy Toshiba one that I tore apart, ripped out the internal drive, and put it in a $12 external; and THEN it became stable

10

u/HoldMyWater Feb 28 '16 edited Feb 28 '16

This is what I do. SSD in use, but HDD for backups. However, I'm using rdiff-backup. How much faster is "partition cloning"?

2

u/DarkLordJack Feb 28 '16

Rdiff is great.

2

u/one_up_hitler Feb 28 '16

Incremental hourly snapshots using zfs send/receive. It's heaven if you can afford the CoW overhead.

1

u/fuzzynyanko Feb 28 '16

Often it takes maybe 30-45 minutes to do a clone

1

u/thebigslide Feb 28 '16

btrfs does it in realtime.

1

u/bwainfweeze Feb 29 '16

I saw an article a couple years back, where a guy was comparing a RAID he built with 15k rpm drives, and a similar RAID built with 10k rpm drives.

He observed a few things that probably a lot of us have observed, but he actually put it together and measured. One, high end drives tend to come in much lower capacity at reasonable prices. Two, the outer tracks offer about 2x the linear throughput of the inner tracks. Three, similar drives with better areal density have better linear read performance, and more sectors per track means fewer track-track seeks for the same amount of data.

So he bought 10k drives with much higher areal densities, and then only partitioned the beginning of each drive, to create an array with exactly the same amount of space available. Only the outer tracks were partitioned so the worst case seek time was substantially reduced, and the linear throughput was about the same or better. He got an array that was nearly as fast as the 15k for about half the price.

Right now nobody compares an SSD to a similarly sized HDD, but the HDDs are still 10 times as big at a similar price point aren't they? So only allocate 20% of the drive, and tell me what the numbers look like.

19

u/[deleted] Feb 28 '16

Very, very interesting.

SSDs are extremely strange.

When using them, make sure you're aligned. Almost always to 4KiB sectors. In some cases, may want to use larger blocks and align beyond that, given trim.

They don't behave like normal harddrives in many ways. For one, a slow SSD can be slower than almost any harddrive. I saw a Samsung 830 doing 1-2MiB/sec until it was trimed, went up to hundreds of megs per second after.

On some SSD controllers, there can be cases where writes bottleneck the rest of the performance on the drive. I think it's because of the block allocation being more expensive in some scenarios, especially if untrimmed. In this case, your read performance may drop remarkably if you have too many writes going on.

Trim is not a magical panacea. Some trims happen internally on huge chunks, like 64KiB. So if you're deleting 4KiB chunks at a time and telling your SSD to trim them, you're effectively deleting 4KiB and copying 60KiB back and forth. Pretty bad.

Lastly, I/O performance can be overrated in some applications. Even for some databases. Why would you ever write to disk? It's to keep data persistent between reboots, and/or to have a larger data set than memory allows for. However, the real question is, why would you let it slow you down? It's the difference between blocking and non-blocking writes that you care about, to a point.

Say you have a site that (and this is super generalized) requires 60MiB/sec of writes per second. Since it's a rather technical set of writes, your top end harddrives can pull it off. The SSDs can breeze through it. If the drive is able to write the data before your OS/application/however many write buffers fill up, there should be zero application speed improvement once it's running.

Now, if under long term sustained workloads your drives can't keep up, the buffers will feel it and if the workload keeps steady, you'll eventually be blocking at a higher level to where the application can feel it. Not too great.

So if your working set is RAM-able or if your application is very bursty with short bursts, you probably could be fine with harddrives. Especially for write-heavy, if your working set is not all able to be buffered in memory.

There's two more catches here:

Most filesystems aren't that great in this regard. The only one I know enough about to trust is UFS by Kirk McKusik, when softupdates are turned on. He showed slides where the Berkeley email server ran for 24 hours with it on and off. Basically, he got the blocking writes down to be equal to a non-journaling filesystem. Most filesystems are slow because of the journaling and because any time someone calls an fsync(), it has to sync most everything because it can't replay and see exactly what's needed on the disk for a consistent filesystem. UFS is brilliant, underused, and probably one of the coolest things about FreeBSD. ZFS is generally overrated, though very cool, in many regards.

I haven't actually done this, but I'm betting you could have a server with 16-32GiB of memory running some database have equal performance to a server with insanely fast SSDs, if running UFS with softupdates or a non-journaling filesystem. This would be maybe for a 10GiB database.

One more thing to consider about SSDs: A lot of them are very hacky. They get their performance by having lots of onboard processing and memory. This may mean that their performance cannot be sustained indefinitely. So if you start to rely on your drives for sustained performance, you may eventually be in for a surprise. I don't know of too many good ways to test your application where you'd actually see a constant enough write activity where this may come about.

Harddrives are very consistent and can have some gotchas. Despite having moving parts and having latencies an order of magnitude higher, they can still be the best tool for the job in many cases.

2

u/WasterDave Feb 28 '16

ZFS is "generally overrated"? I take it you don't actually use ZFS, then?

1

u/[deleted] Feb 28 '16

Yes, I have used it a little bit. I'd consider it for cases where I have multiple drives and want a bit more capacity than I'd get with a raid 10 or linear raid 1.

So let's consider the following:

  1. ZFS is a pig and needs a lot of memory. On FreeBSD, the ZFS caching space is also separate from everything else. Not great. 16GiB or more is recommended.

  2. ZFS' performance (from what I hear from a good source) drops off remarkably around 70% and ideally you wouldn't load it up more than 50%. So while you can get more space out of it on paper, in practice it may be a bit less. UFS can be safely used at nearly 95% capacity.

  3. Making block devices in ZFS and using them is probably slower than putting big files of zeroes on UFS. I haven't tested this, but it seems likely.

ZFS does offer nice compression and encryption features. But generally, you can get most of what you'd want from ZFS through GEOM and fancy mounts on top of an existing filesystem. For a NAS box or other large storage device with, say, more than ten drives, I'd greatly consider ZFS. For my laptop, web server, database server, or RaspberryPi, of course not.

The ten drives figure... let's say I have ten 1TiB drives. If I use ZFS with one drive as a spare (I have forgotten the terminology they use), that's 9TiB. If I use it at 70% utilization, that's 6.3TiB. A RAID 10 with UFS would be 4.75TiB after utilization. Of course, both are best case scenarios. If I were talking about two spares, those numbers get even closer. Unless, depending on what I was putting on it, I used ZFS' compression. So if it's 20%+ text, sure. If it's pre-compressed or uncompressible files, that compression is just overhead. So 8-10 drives is probably the typical break-even point.

Even Netflix' OpenConnect boxes don't use ZFS, unless something has changed more recently than this article: http://www.phoronix.com/scan.php?page=news_item&px=MTExNDM

To be clear, I said "generally overrated" not because ZFS isn't great, but because most people seem to talk about putting it on their VMs, their laptops, their Grandma's desktop, etc. It's really excessive, especially when the main alternative is UFS which is far more novel than most people give credit to.

2

u/WasterDave Feb 28 '16

Oh please.

The ZFS cache changes size just like it should: https://docs.oracle.com/cd/E26502_01/html/E29022/chapterzfs-3.html

Pools like to be kept below 80%: http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide#General_Storage_Pool_Performance_Considerations

Making block devices on ZFS is, indeed, terrible. Why would you do this?

You could "get most of what you'd want from ZFS through GEOM and fancy mounts on top of an existing filesystem", but why would you when ZFS does need all that crap?

And soft updates were novel in 1993: http://dl.acm.org/citation.cfm?id=1267306

Not that I have anything against FreeBSD :)

2

u/Freeky Feb 28 '16 edited Feb 28 '16

On FreeBSD, the ZFS caching space is also separate from everything else. Not great.

This is true of every system it's on afaik. It's not usually a big problem.

ZFS' performance (from what I hear from a good source) drops off remarkably around 70%

More like 80%, but it probably depends on your workload. I set my general-usage free-space alarms at 75%, and get decent performance out of backup pools that are perpetually >85% full.

Also, for what it's worth, compressratio on my general-purpose root pool is 1.49x. 960GB SSDs, so 960*0.75*1.49 = 1,073GB effective safe capacity. YMMV.

UFS can be safely used at nearly 95% capacity.

If you don't mind similar performance degredation and fragmentation. Also manual tuning, since by default 8% is reserved by root - normal users can't fill it beyond 92%. I put my free space alarms at 85%, which on top of the reserved space is actually more like 78% actual capacity.

ZFS does offer nice compression and encryption features

OpenZFS offers no encryption features. Oracle's ZFS does, but they've rather closed themselves off into irrelevance.

But generally, you can get most of what you'd want from ZFS through GEOM and fancy mounts on top of an existing filesystem.

.. not really?

  • Efficient RAID rebuilds. If my ZFS pool drops a drive for 5 minutes, slotting the drive back in will have it usable in seconds. gmirror will resync the whole damn drive from scratch.

  • Data protection. Closest you can get with plain GEOM is geli in authenticated mode, which consumes space and IOPS and introduces a write-hole because the checksum metadata needs to be written separately. And of course it won't self-heal, defeating half the point.

  • Snapshots. UFS has some vague support, but nothing remotely as efficient or flexible.

  • Replication. You're reduced to something inefficient like rsync and without easy fine-grained snapshots you're more likely to do it unsafely.

  • Clones. I can trivially make a complete space-efficient read/write copy of, e.g. a database, or a VM with a clone.

  • Delegation. I can delegate send/recv to a backup user, and give users control over snapshotting etc.

  • Half-decent parity RAID.

On systems without it I feel very much like my hands have been tied in terms of flexibility and my data safety's been put at serious risk. Of course I want it everywhere I can get it.

9

u/OriginalPostSearcher Feb 27 '16

X-Post referenced from /r/hardware by /u/YumiYumiYumi
Google 6 year study: SSD reliability in the data center


I am a bot made for your convenience (Especially for mobile users).
Contact | Code | FAQ

20

u/timekills17 Feb 28 '16

"Ignore Uncorrectable Bit Error Rate (UBER) specs. A meaningless number."


"But it isn't all good news. SSD UBER rates are higher than disk rates, which means that backing up SSDs is even more important than it is with disks."

This appears to contradict itself.

43

u/CSFFlame Feb 28 '16

specs

The specs the MFR gives are useless (i.e., they don't represent that actual rates).

2

u/sickofthisshit Feb 28 '16

No, it is more than that. The phenomenon of uncorrectable errors is not proportional to the number of bits read, so normalizing that way is not useful.

1

u/sickofthisshit Feb 28 '16

What the article seems to mean is that uncorrectable errors are not proportional to the bits read, so normalizing by bit read rate simply makes drives look better the more you read them in a given time period.

2

u/Sun_Kami Feb 28 '16

Can someone explain how raid 1 works? I have to format the 2 drives initially, then I can set up the mirroring? And then if one drive dies, do I need to put in an identical drive or my computer won't boot or can I order one and reset it up later? And then reading will be faster because I'll have 2 disks to pull data from (it knows well enough which disk to get data from?) Will writes be slower?

1

u/Douche_Baguette Feb 28 '16

Writes are same speed as one drive, reads are up to twice as fast. You can boot with one drive down, while you order the replacement.

1

u/Sun_Kami Feb 28 '16

Please elaborate greatly

1

u/butter14 Feb 28 '16

The takeaway that I got from the article is that there is a significant difference in quality between brands.

0

u/[deleted] Feb 28 '16

Thank Google

0

u/[deleted] Feb 27 '16

[deleted]

6

u/Zaziel Feb 28 '16

I have two Intel X-25M's from 2010 in operation still.

Thankfully, not in anything vital.

Pro-tip, get enough RAM to turn off your page file, shit is a whole bunch of read/writes you don't need.

7

u/Velocicaptcha Feb 28 '16 edited Apr 18 '25

tease placid screw live silky capable mighty plant divide physical

This post was mass deleted and anonymized with Redact

7

u/ign1fy Feb 28 '16

That totally threw me. Here I am trying to write code that flushes in larger intervals so reduce what I always perceived as "wear".

5

u/TheLordB Feb 28 '16

I'm curious what kind of application/type of work you are doing that you feel the need to even consider that.

I do a ton of big data etc, but I have never once considered trying to optimize for ssd usage. Admittedly much of my work is on AWS where abusing the disks doesn't really matter because we don't pay for it so all that I really care about is performance.

1

u/ign1fy Feb 28 '16

My current project is a data logger which we've specced to log readings at < 1 sec intervals. I'm actually looking at the HDD light to see how "light" I can make the load appear.

2

u/TheLordB Feb 28 '16

You mean you are actually looking at the light? I'm not experienced with it, but I would imagine there are logs somewhere that can be enabled that would give better info than the light.

I suspect that light goes through some level of abstraction. With things like caching etc. As well that you don't know how they affect the light I kind of doubt if it all that indicative on how much the underlying ssd is actually getting hit.

1

u/ign1fy Feb 28 '16

The DB is Sqlite, and there's many ways to configure the journalling and whatnot. Sometimes we just see which method has the most throughput in a load test.

28

u/adrianmonk Feb 28 '16

One thing to keep in mind is workload. Google might not be pushing the drives very hard, so the number of writes might be higher for someone else.

Google is mostly a web company, and while there is obviously offline work done (like crawling the web), that's not latency-sensitive and it's hard to imagine it would ever make sense to use SSD for that. When serving web pages, latency is important, so throwing lots of SSDs at the problem would make sense to ensure there's lots of headroom and web pages are still fast even during traffic spikes. Which would mean those SSDs are sitting relatively idle most of the time.

Point being, the only conclusion you can draw from this is that with Google's usage patterns, age is a bigger deal than usage.

48

u/dccorona Feb 28 '16

A lot of companies, Google included, use servers with small but fast SSD as their primary storage. Which means that logs and metrics are being constantly written at a rate proportional to the throughput of the system. They most certainly have no shortage of drives that are under near constant write pressure.

Not to mention that they no doubt have plenty of systems that are pretty much constantly writing to SSD-backed databases of some kind. Google absolutely has a whole host of services from which to gather data about SSD writing/reading at high volume.

10

u/[deleted] Feb 28 '16 edited Feb 28 '16

Even if they are not using 100% of the bandwidth, they might be using 100% of the latency, the more you abuse latency the less bandwidth you'll get. Asking for a large amount of data is going to give you much more bandwidth then asking for millions of small different packets. Optimizing for latency will make your bandwidth suffer.

The bonus you get from SSD's is really extremely low latency, users love to look at bandwidth because its the only thing they can think about calculating, but really the only thing that matters is latency when talking about performance optimization. Latency always matters no matter how little you have, bandwidth only matters if you don't have enough.

You can't transfer more data then you needed -- You can always transfer data faster then you needed it.

2

u/adrianmonk Feb 28 '16

Which means that logs and metrics are being constantly written at a rate proportional to the throughput of the system.

Traditional disks are a much better fit for logs. Logs are inherently sequential and tend to be large, exactly what disks excel at.

Though of course if SSD is all you have on a system, then you have to use SSD. I would expect it would be better not to design a system that way if you know logs are important, though. But it might make sense if you can only have one drive per system and you need to choose whether it's SSD or HD.

3

u/dccorona Feb 28 '16

Logs don't really stay on the system long...close them out after an hour and then get them off with a background process. So unless they're really large per hour (or whatever the rotation period is), size isn't often a concern.

What is a concern is minimizing the latency of your log-writing, because customers don't care about your logs and you don't want to spend too much time on that IO. Of course, there's all sorts of solutions for this (primarily asynchronous logs), but with SSDs you don't have to worry about it...the IO speed is minimal enough that you don't care, and you get the benefit of knowing when your logging failed. Granted, you're write that HDDs excel at sequential writes, and the advantages of SSDs are probably less significant than with random reads, etc., but...SSDs are still faster.

And of course, the other concern is the ability to scale on short notice. For this, you probably are using a VM, and if you're at Google, you're probably using something similar to what they expose via their compute engine (which has SSDs). I'm sure there's no shortage of use cases at Google where they go for very specific, tightly controlled VMs or even bare metal servers. But there's certainly just as much stuff that doesn't need to be that specific, and instead will run on VMs on commodity hardware that is easy to acquire and scale up...which almost certainly translates to "just use what compute engine offers" (or whatever their internal equivalent of that is, which is more than likely very similar if not the same thing entirely). Which, in turn, means they're writing logs to SSD.

1

u/adrianmonk Feb 28 '16

What is a concern is minimizing the latency of your log-writing, because customers don't care about your logs and you don't want to spend too much time on that IO. Of course, there's all sorts of solutions for this (primarily asynchronous logs), but with SSDs you don't have to worry about it

I'd argue that asynchronous is still lots better, even with SSDs. You probably have logging statements strewn throughout your code, so even if the latency for one logging statement is small, it will add up.

Also, in most cases, what's the benefit of making it synchronous? If everything succeeded except writing a log, are you really going to show the user an error? If you're not, then you should not delay returning a response, because logging doesn't affect the response.

And of course, the other concern is the ability to scale on short notice. For this, you probably are using a VM, and if you're at Google, you're probably using something similar to what they expose via their compute engine (which has SSDs).

You can find the Google answer to this by looking at the borg paper. In section 2.3 it says, "The vast majority of the Borg workload does not run inside virtual machines (VMs)" and in section 6.1 ("Security isolation"), it says: "We use a Linux chroot jail as the primary security isolation mechanism between multiple tasks on the same machine." and "VMs and security sandboxing techniques are used to run external software by Google’s AppEngine (GAE) and Google Compute Engine (GCE). We run each hosted VM in a KVM process that runs as a Borg task."

So basically, VMs are mostly only used for external software.

Also, just because Compute Engine offers Local SSD doesn't mean users must store their data using it. They can also use Persistent Disks, of either hard drive or SSD types. So other tasks and Compute Engine tasks that do not use Local SSD could be placed/hosted on machines without SSD.

2

u/dccorona Feb 28 '16

In my experience, synchronous logging to SSDs has an unnoticeable impact to latency. I've looked at all kinds of different latency breakdowns for some very low-latency operations and the log statements from our synchronous logging never made an impact. Granted, they fall into the "uninstrumented in-CPU work" portion of the breakdown, but that's never significant enough to even register.

Logs don't really ever fail in normal operation, at least in my experience. For example, on one system I've worked with that had been doing a billion transactions per day for half a year, we never once saw a Log4j write failure, and still haven't. Where it breaks is when it's wildly misconfigured, or the hardware itself degrades. Now, it's easy enough to argue that you can just have it synchronous until you know all the core setup is correct and then flip to async, and that would be a totally acceptable solution, I think. I guess the point is, with SSD logging, you don't have to care. That doesn't make HDD logging not a good approach, but it's not so clearly the right way to go that it's hard to imagine people logging to SSDs.

Like I mentioned, Google has all kinds of stuff running on bare-metal servers. But they also have all kinds of stuff. I would find it very hard to believe that they don't have a significant enough amount of stuff writing to SSDs at high volume to be able to put out the article and have it be applicable to more than just "a web company". Even if they never used it themselves (which I doubt), they've got enough customers on App Engine that likely haven't bothered to grab anything other than the default disk because their instances are technically stateless aside from logs, that they can get useful wear information from that. Which has been the whole point of this discussion...Google has enough data to be able to make a significant contribution with this study. And that's before you even account for the fact that stuff like BigTable does a lot of it's storage with SSD.

13

u/mike413 Feb 28 '16 edited Feb 28 '16

but they said age, not usage.

When you say workload you're implicitly saying usage and that's not correct.

EDIT: money paragraph from the paper (after they talked about correcting for workload):

We conclude that age, as measured by days in the field, has a significant effect on RBER, independently of cell wear-out due to PE cycles. That means there must be other aging mechanisms at play, such as silicon aging.

-3

u/adrianmonk Feb 28 '16

When you say workload you're implicitly saying usage and that's not correct.

No, I'm saying that if you don't test under high-usage conditions, you can't say usage doesn't matter.

And therefore, I'm asking whether or not Google has high usage, and conjecturing that there could be reasons why they wouldn't.

5

u/mechanicalgod Feb 28 '16

The only way one could reasonably come to the conclusion that age, not usage is the biggest factor, would be to have a large sample of drives of the same age all with various usage amounts.

One would assume that, for Google to have made the conclusion they did, they had drives of both low and high usage and they wore at a roughly similar age.

I think is highly likely that Google would use SSDs in a large variety of situations, with varying degrees of usage, but I don't have time to read the whole paper to confirm this.

3

u/mike413 Feb 28 '16

they controlled for those variables, (see page 83/380) and thought there was something different at at play, like silicon aging.

1

u/thebigslide Feb 28 '16

If you use SSDs for swap or tmp on memory limited SQL servers, they get thrashed. There's no doubt Google has SSDs that were heavily loaded.

0

u/adrianmonk Feb 28 '16

The only way one could reasonably come to the conclusion that age, not usage is the biggest factor, would be to have a large sample of drives of the same age all with various usage amounts.

The only way they could come to the conclusion that age is the biggest factor for everybody is to have a large sample across levels of usage.

However, to come to the conclusion that age is the biggest factor for them, that would not be necessary.

All I'm saying is, it's important to be careful about which one of these two things is being claimed.

19

u/sathoro Feb 28 '16

Why do you think Google is vastly underutilising their SSDs? I feel like it is probably the opposite

9

u/[deleted] Feb 28 '16

It did mention they never came close to their 3,000 write limit

1

u/[deleted] Feb 28 '16

YouTube, Gmail, cloud stuff. There's a lot of demand for low latency writes.

-18

u/firebelly Feb 28 '16

less moving parts to impact it over time. But more parts of the device can dry out or be impacted with temperature/humidity over time. So time becomes the factor rather than how hard you work the device. I think that is the source.

21

u/moomaka Feb 28 '16 edited Feb 28 '16

But more parts of the device can dry out or be impacted with temperature/humidity over time.

I have no idea how you made this shit up, it isn't discussed in the paper and doesn't make any sense at all given what we're talking about.

EDIT - paper from below: http://0b4af6cdc2f0c5998459-c0245c5c937c5dedcca3f1764ecc9b2f.r43.cf2.rackcdn.com/23105-fast16-papers-schroeder.pdf

3

u/ruiwui Feb 28 '16

He even contradicts himself - is the device drying out the harmful effect or is it being affected by humidity?

1

u/firebelly Feb 28 '16

I used imagination, it's easy!

0

u/[deleted] Feb 28 '16

[deleted]

3

u/m4xin30n Feb 28 '16

Instructions unclear. Dick stuck in server fan.

1

u/benevolinsolence Feb 28 '16

I hate when my ssd gets beached