.
Re: Best config for NLE with SSDs, big spindles, 8GB RAM?
Sorry jxf011 but no one is going to be able to tell you what the best config for your setup is unless they have the exact same setup. It takes time and a lot of testing to optimize a system and storage is especially tricky..
Personally I'd leave all the RAM for your video rendering, but if you want to see how much ram you can spare do a test render of a big project and run a Perfmon to monitor & log your ram usage. If you find that you have some unused ram, use a portion of that for L1 cache in Fancycache..
Next keep in mind that Fancycache will only cache something that has been read of the disk first and this cache is not persistent across reboots. So lets say you start up your system, load up a project that has 30 clips sitting on your HDD drive and you try to render them, you'll be reading them a drive speed not L2 SSD speed. BUT lets say you've have the project open all day, you have a nice big L2 cache and you've been playing the playing the clips. Everything that has been played/read off disk should be in your cache. Now when you got to render you'll utilize the caching system. This is supposed to change with a future update, where F.C will get persistent caching.
F.C isn't a silver bullet for slow HDDs, when it does it's thing it's blazing fast but it can be hit or miss based on the application you're using and how it uses the storage system. The big gotcha that confuses users is it doesn't predict what you'll need, so it won't preload data for you and for most users (though this probably doesn't apply to you) the data they need is rarely used more than once (such as games) so it loads at HDD speed.
I don't usually say this to most users but if you do this professionally or are a serious hobbyist you really might want to consider a new system (if you feel yours isn't cutting it anymore). The time that you'll save doing big renders and just daily workflow improvement will make it more then worth it. For you the big jump will be CPU architecture (which has change dramatically since the 4 core) and the ability to utilize a HUGE amount of ram (64gb would do a LOT for you).
Personally I'd leave all the RAM for your video rendering, but if you want to see how much ram you can spare do a test render of a big project and run a Perfmon to monitor & log your ram usage. If you find that you have some unused ram, use a portion of that for L1 cache in Fancycache..
Next keep in mind that Fancycache will only cache something that has been read of the disk first and this cache is not persistent across reboots. So lets say you start up your system, load up a project that has 30 clips sitting on your HDD drive and you try to render them, you'll be reading them a drive speed not L2 SSD speed. BUT lets say you've have the project open all day, you have a nice big L2 cache and you've been playing the playing the clips. Everything that has been played/read off disk should be in your cache. Now when you got to render you'll utilize the caching system. This is supposed to change with a future update, where F.C will get persistent caching.
F.C isn't a silver bullet for slow HDDs, when it does it's thing it's blazing fast but it can be hit or miss based on the application you're using and how it uses the storage system. The big gotcha that confuses users is it doesn't predict what you'll need, so it won't preload data for you and for most users (though this probably doesn't apply to you) the data they need is rarely used more than once (such as games) so it loads at HDD speed.
I don't usually say this to most users but if you do this professionally or are a serious hobbyist you really might want to consider a new system (if you feel yours isn't cutting it anymore). The time that you'll save doing big renders and just daily workflow improvement will make it more then worth it. For you the big jump will be CPU architecture (which has change dramatically since the 4 core) and the ability to utilize a HUGE amount of ram (64gb would do a LOT for you).