2 dual/quad cpus vs 1 quad/octi cpu

Aug 6, 2018
1
0
10
I have been thinking about buying a computer for both gaming and deep learning projects, and as a result I have been at a standstill as to how to prioritize my build. My budget is $3000 and I am building my pc myself. I have known about dual cpu setups and I was curious why they are not more common. To me, it just makes sense to spread out cores over more space to get better cooling and larger cores and therefore better performance per core. Since this is not a popular market choice, however (and neither are pancake sized cpus), this option is definitely more than twice as expensive. However, I am wondering whether, assuming equivalent performance to just doubling cores, the ability to be smart about shopping for 2 cpu's that are a better value than the higher core cpu would offset the cost of a dual cpu motherboard etc. If so, what would be good for a noob enthusiast? (I am wondering if dual gpu's are a better value)
(here's an old link to an article showing dual cpu performance is about the same as dual core)
https://www.pugetsystems.com/labs/articles/Dual-Processor-vs-Dual-Core-23/
 
Solution
Dual socket CPUs have the problem that communication between the two sockets is much (much much) slower then between threads on the same die.
If this isn't a problem at all then you can just as well build two (or x) systems and link them up via network,if it is an issue there is nothing you can do about it.
For games for example this is a very big issue because they have to sync up all the threads to display each frame and having to wait for the threads from the other socket would take a while.

Your best bet would be to build a fast cored system for gaming and have a second basic build with no dGPU/monitor but as many cores as possible even if they are weak,basically a render(deep learning) box that you would send your projects to from...
Dual socket CPUs have the problem that communication between the two sockets is much (much much) slower then between threads on the same die.
If this isn't a problem at all then you can just as well build two (or x) systems and link them up via network,if it is an issue there is nothing you can do about it.
For games for example this is a very big issue because they have to sync up all the threads to display each frame and having to wait for the threads from the other socket would take a while.

Your best bet would be to build a fast cored system for gaming and have a second basic build with no dGPU/monitor but as many cores as possible even if they are weak,basically a render(deep learning) box that you would send your projects to from your main build.
 
Solution