Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cache spinner vs. SSD

Featured Replies

This might not be exclusively related to Docker, but it definitely is a component...

 

Having recently made the migration to v6, I'm now wondering what I should do with a 250GB SSD that I am currently not using.

 

At present, I have a 1 TB WD Black for my cache drive (never need that size, but that's what I pulled from an old PC build).  This bad boy is probably 6 or 7 years old and is still going strong despite consistent hammering by unRAID use over the years.  Though its served me well, I'm wondering if I should swap out to the SSD for my cache drive.  Or perhaps just use SNAP and add the SSD outside of the array for Docker containers/data.

 

The only issue that worries me, possibly unnecessarily, is repetitive writes to the SSD with apps like sabnzbd.  I have 2 SSDs in my ESXi build as datastore drives, but I have tried to pull off a lot of the temporary file duties (of Plex transcoding, for example) to spinners.  Maybe I'm being overly cautious.  Thoughts?

 

Thanks in advance!

No modern SSD is likely to be an issue with the write volumes you're likely to see from sabnzbd.    SSDs are very reliable until you cross about 500TB or so of write activity ... and many can easily exceed 1PB.

 

By the time you get to those levels, I suspect you'll be replacing it with a much higher capacity SSD  :)

Everyone has their own opinion on this, but I personally think you're being overly cautious.  Is the repeated hammering a cache drive takes going to wear it out sooner than later?  Yes, it will, but current gen SSD's have very high endurance ratings compared to older SSD's.  On top of that, in extended testing they generally last FAR beyond the manufacturer's endurance rating (to the tune of several hundred TB, some even surpassed 1PB).  That said, I'd personally stay away from the bargain basement SSDs and stick with one of the quality SSD manufacturers like Samsung, Intel, OCZ, etc.  The additional benefit of using an SSD for your cache, besides the obvious much faster performance, is lower power consumption and less heat generation.

 

I just recently replaced a spinner cache with an OCZ ARC 100 Series SSD.  The manufacturer endurance rating on that drive is 20GB/day for 3 years.  That works out to roughly 22TB before the drive is outside the endurance rating, and will likely continue to work far beyond that number.  Even if it were to fail after 22TB of writes, I'd simply replace it with another SSD. 

 

 

  • Author

Thank you both for the input.  I figured I was being overly cautious. 

I run a SSD for Docker and downloads, and use a 2.5" HDD for my cache, as it spends most of the day spun down anyway.  Specs in my signature.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.