Submariner wrote in post #17988499
Hi
Thanks Doc, thats most encouraging news. And all the details so much appreciated
Obviuosly thats why they didnt highlight it too much in the manual.
My plan was to stick to 32GB till I start rendering 4K video say in a year ( my 5DS R only does 1080p )
I have an Intel 750 PCIe for Win 10 and Programs and the current shoot. I have 2x samsungs 850 evos 500GB to copy the current shoot to when I complete editing.
I was going to buy the 950 Pro, bit seeing the high heat at the M2 connector think I prefer to buy another intel 750 when my supplier has another sale.
Lets hope this MB works :-/
Very good choices in hardware. I've been designing high performance/reliability boxes for over 20 years. I'm also a low-level coder, mostly asm and C++ work while doing some .NET stuff for databasing and parallel image processing code (medical imaging). The same box runs my Lightroom/Capture One/Photoshop/InDesign stuff. Stick to the good stuff and it'll last a long time...my boxes get pounded hard day after day and I've routinely had RAM loads > 24GB constantly.
I use the i750 drives, as well as the 850 Pros (the evos are ok for desktops, but do not like RAID - they use an SLC buffer to give the feeling of speed. In the long run, the Pros are "pure" speed. Since RAID isn't about direct file transfers, the evos go nuts after a while and will slow down). As far as other hardware, I stick to Supermicro boards, Intel Xeon procs, Micron or Samsung RAM, NVIDIA Quadros, and Seasonic 1.2kw+ power supplies. There's no advantage to liquid cooling either - a good set of Panaflo or Delta fans do the job perfectly; just remember that the CFM of the exhaust fans should be close to the amount of cold/room air that is entering the case, otherwise you'll have a vacuum and not cool anything (look at the gamer kiddies with their 10 fans sucking air out, but little air coming in!)
For archival data, I use physical SAS 15K drives in a fiber channel NAS RAID'd for storage. A bad drive can still be repaired, but most SSDs cannot be recovered as easily. It's still important to have a good backup plan to keep the data. My LR catalog is around 5GB and the images folder on this box is sitting at about 2.8TB currently, and it loads, runs smoothly
The trick is to find the bottlenecks in the system and address them. It used to be the main bottleneck was the disk path. With SSDs, that's gone away. RAM bandwidth is rarely an issue nowadays. The bus speed was a bottleneck for some time, but with QPI, that's going away. It's now down to the poorly written/optimized software that is moving data (very rapidly) into the processors and causing cache thrash.
With video, the graphics card can be a bottleneck, if the system doesn't have a hardware encoder for the output. Matrox makes quite a few hardware MPEG encoders, as well as other formats, that can help that offload. Adobe Premiere takes advantage of many of these. Also, with Sony Vegas, you can also split your rendering across multiple boxes over a network connection, so that "cluster render" can also help. Of course, with CUDA and OpenCL, GPU assisted rendering *can* be faster than pure CPU rendering, but not always - a small, slow card can also be slower. The hardware encoders are still the best choice.
Hope that gives you some insight!