It's substantially faster than the Samsung 960 Pro 2TB in my old workstation but that won't make any difference.
Having 128GB of memory means there's a massive amount of cached data and plenty of space to buffer writes.
Latency is something that does matter a lot though.
Conversation
RAID hurts latency and IOPS. It's not really suited to the age of high-end NVMe drives. It's also really hard to actually be I/O bound with this kind of drive.
Latency is what really ends up bottlenecking performance for I/O for anything that I'm likely to do, not the rest.
2
Replying to
Good to know, Im resurrecting a development WS myself next week based on 2010-ish HP CAD CAM stations still laying around. If that doesn't perform I need to save up for what you did here.
1
Replying to
Basically, if you have mostly CPU-bound tasks, it's very wasteful to make far more threads for them than you have cores. You really don't want to be context switching. Data is ideally almost always cached and there's generally enough write buffer that write latency is irrelevant.
2
My biggest cou loads used to be VB macro churning within high end CATIA or UNIGRAPHICS env, imagine that. 2x4 multicore xeon pkus 96GB did help though. But horrible still
1
Replying to
My current workstation is a build from 2016 with a i7-6950X overclocked substantially (4.5GHz), 64GB DDR4 and a Samsung 960 Pro 2TB.
I wanted to replace it much earlier with Zen 2 Threadripper but I couldn't get the parts. Kept getting delayed until it made no sense anymore.
1
The 10 core i7-6950X is competitive for full build compilation with a 24 core Xeon from the same generation and is substantially better for most incremental builds where it's heavily bottlenecked on a couple threads.
It was really good for a couple years but it's awful now.
1
When Zen 3 Threadripper comes out, I'll happily pay thousands of dollars to get a 64+ core CPU, nice motherboard and 256GB+ memory to go with it.
Could not wait any longer though, and I'll happily turn this into a replacement for my badly aging gaming PC so it won't be wasted.
1
Also, for the time being, I'm going to switch to dual booting on this machine while still also using my older workstation. So, I can either have 2 workstations doing builds or I can be doing gaming on this while also switching over regularly to test new builds on the other, etc.
2
Since I'm often waiting for builds, I need to multi-task, and there's a limit to how many different development things I can manage at a time. I only like working on a couple things at a time and waiting for the builds/tests.
I work while consuming TV/movies, etc. Works well.
The worst is waiting for stuff to be tested across phones. The test harness knows how to spread out tests across multiple phones but it still takes ages and I only have a single USB-C port able to fast charge while testing so the other ones will trend towards battery dying.