OTOY Forums

haknslash wrote:SSD lifespan

Glimpse wrote:SSD lifespan

Don't want to flog a dead horse by continuing this topic; but SSD lifespan concerns which lead to 'SSD Optimisation guides' in 2011/2012 were largely related to old technologies, new SLC based drives have much larger 'garanteed write cycles' - at which point those cells are 'trim'ed off the drive...

So your SSD doesn't 'just die' it actually slowly starts to reduce in size as each cell is determined to be not operating within the speed/efficiency/whatever constraints by the firmware.

Last time I looked at it; because I was worried about dropping $2/Gigabyte; I estimated I'd get well over 5 years out of my 128gb SSD, before its reduced size & speed affects my work - longer than I usually keep any drive anyway - and the speed improvement for those 3-5 years effective lifespan make up for the hassle of migrating in 5 years time. (Edit: PLUS; there will probably be 1tb SSD drives by then, and we'll all be working with 4k Res assets at a minimum!

also; fwiw, I use 1 x 128gb SSD for OS & Apps (+swap & OS reserved), 1 x 256gb SSD for project data, library/assets (+swap): and both those drives backed up to my RAID0+1 which is where I also store all my personal files/home videos/etc.
also ALWAYS ALWAYS ALWAYS keep an off-site backup.

As stated above by Glimpse & Haknslash a Single SSD (512gB probably realistic these days) + Mechanical for backup & non-speed critical stuff (ie video & music data rates are FAR FAR lower than max data rate of a mechanical drive)

probably too much detail - but degradation/trimming is not a reason not to g4et the 10-20x speed increase of SSD on all your project & Program files... We're professionals after all...

The Dell Ultrasharp 27" U2713HM Monitor is a very nice monitor, it's from december 2013, for me that is really new...
I don't use 4K because I can't see what I'm doing, everything is just too smal.

I start with a single monitor setup.
And as soon as it is possible, because I;m rebuilding my house, I'll use a dual monitor setup.

Good exercise for my neck...

In regards to the VRAM, will you be rendering from Octane Standalone or from within a 3D app plugin, say C4D? Also, what resolutions will you be rendering at? I ask because those answers play an additional role in how much VRAM you need, besides just poly count. Running inside a plugin will take up more VRAM than standalone. In MODO it uses about 1GB more for the interface, textures, etc. Also, very high resolutions will use up more VRAM than the same scene at smaller resolutions. It's an extreme example, but just this week I had to render an image out at 10K pixels wide. The 2K version used only 200+ MB of VRAM, but moving to 10K needed over 2.5GB. Big difference. Granted, most will never need that size, but increasing resolution also increases VRAM requirements. Might be worth doing some tests.