F5F Stay Refreshed Hardware Desktop No, I don't have any experience with Xeon E5-2696v2.

No, I don't have any experience with Xeon E5-2696v2.

No, I don't have any experience with Xeon E5-2696v2.

P
Pauxyneu
Member
138
02-20-2016, 05:14 AM
#1
It seems the CPU is an OEM model, but its spec closely matches the E5-2697v2. Many users have shared their experiences with it. You're upgrading from 32 cores to 48 cores, which should boost performance significantly beyond just the multiplier. Expect faster boot times, smoother multitasking, and better handling of demanding applications like NVMe SSDs while coding in Eclipse.
P
Pauxyneu
02-20-2016, 05:14 AM #1

It seems the CPU is an OEM model, but its spec closely matches the E5-2697v2. Many users have shared their experiences with it. You're upgrading from 32 cores to 48 cores, which should boost performance significantly beyond just the multiplier. Expect faster boot times, smoother multitasking, and better handling of demanding applications like NVMe SSDs while coding in Eclipse.

M
MineArqueiro
Member
237
02-23-2016, 03:16 AM
#2
It seems you're questioning the efficiency of current code. Would it help to explore if additional processing cores are necessary?
M
MineArqueiro
02-23-2016, 03:16 AM #2

It seems you're questioning the efficiency of current code. Would it help to explore if additional processing cores are necessary?

T
Texas1047
Posting Freak
889
02-23-2016, 04:11 AM
#3
I'm not sure about the current core usage in Cities: Skylines, since its agent-based engine supports heavy parallel processing if done correctly.
T
Texas1047
02-23-2016, 04:11 AM #3

I'm not sure about the current core usage in Cities: Skylines, since its agent-based engine supports heavy parallel processing if done correctly.

D
DuyD
Member
176
03-02-2016, 03:45 AM
#4
It seems unlikely an e5 2680 would have been utilized to its full potential. Overlook the need for dual CPUs in gaming; most engines operate without detecting a second node. Overall, for the scenarios you mentioned, the upgrade won’t make much difference.
D
DuyD
03-02-2016, 03:45 AM #4

It seems unlikely an e5 2680 would have been utilized to its full potential. Overlook the need for dual CPUs in gaming; most engines operate without detecting a second node. Overall, for the scenarios you mentioned, the upgrade won’t make much difference.

J
Jelly_Fluff
Member
54
03-02-2016, 06:21 AM
#5
Code compilation appears to be improving since it involves multiple compilers operating concurrently. The "-j48" flag indicates 48 instances of GCC are being used.
J
Jelly_Fluff
03-02-2016, 06:21 AM #5

Code compilation appears to be improving since it involves multiple compilers operating concurrently. The "-j48" flag indicates 48 instances of GCC are being used.

V
vuro
Member
244
03-04-2016, 07:26 AM
#6
The compiler supports multiple CPU nodes.
V
vuro
03-04-2016, 07:26 AM #6

The compiler supports multiple CPU nodes.

L
LOVAC13
Member
108
03-04-2016, 08:05 AM
#7
GCC runs one thread at a time by default, but using GNU make can create several GCC instances simultaneously. The "-j" flag specifies how many to launch at once, so "-j48" runs 48 copies.
L
LOVAC13
03-04-2016, 08:05 AM #7

GCC runs one thread at a time by default, but using GNU make can create several GCC instances simultaneously. The "-j" flag specifies how many to launch at once, so "-j48" runs 48 copies.

L
luxrox
Member
227
03-04-2016, 10:47 AM
#8
Interesting. With my dual CPU setup, it kept ignoring CPU1 for compilation or just didn’t work at all—cpu0 or not. Looks like things have improved.
L
luxrox
03-04-2016, 10:47 AM #8

Interesting. With my dual CPU setup, it kept ignoring CPU1 for compilation or just didn’t work at all—cpu0 or not. Looks like things have improved.

K
kbolt
Member
238
03-06-2016, 09:35 PM
#9
Switching from 32 to 48 threads lets you create 50% more GCC instances concurrently, which reduces compile time and increases stress on your NVMe SSD. All these GCC instances will be handling numerous small files—source code and headers—as well as generating many object files simultaneously, raising the SSD IOPS demand. This is why I adjusted my BIOS to enable NVMe booting for the C602 (similar to X79) chipset.
K
kbolt
03-06-2016, 09:35 PM #9

Switching from 32 to 48 threads lets you create 50% more GCC instances concurrently, which reduces compile time and increases stress on your NVMe SSD. All these GCC instances will be handling numerous small files—source code and headers—as well as generating many object files simultaneously, raising the SSD IOPS demand. This is why I adjusted my BIOS to enable NVMe booting for the C602 (similar to X79) chipset.