Live data from Hacker News

An EPYC NixOS Build Farm

grahamc.com

11–20 of 37 posts

Re: An EPYC NixOS Build Farm

#11
post #10
post #9

I'm curious if anyone knows the test tool they're using here, in particular for lines like: $machine->waitForWindow("^Desktop "); It looks incredibly useful. Thanks!

Well there seems to be something called nix-shell, but I never heard of it before. It seams pretty useful. The link to plasma tests is provided in the article. https://github.com/NixOS/nixpkgs/blob/49a6964a4250d98644da61...

Thanks!

Re: An EPYC NixOS Build Farm

#12
I wonder if there were NUMA effects at play since the Intel server was dual-socket and the EPYC was not. It's not entirely surprising that a CPU-heavy workload reading from filesystem cache (i.e. memory) could cause a substantial amount of nonlocal reads that the single-socket server wouldn't have to deal with.

That said, that's just the first thing that popped into my head to explain the result. Either way, the results here are extremely encouraging!

Re: An EPYC NixOS Build Farm

#13
Unless your buying top of the line Intel parts AMD is going to have more performance at most price points. It's the only logical decision unless you use AVX-512 or your workload is single threaded.

Re: An EPYC NixOS Build Farm

#14
post #12

I wonder if there were NUMA effects at play since the Intel server was dual-socket and the EPYC was not. It's not entirely surprising that a CPU-heavy workload reading from filesystem cache (i.e. memory) could cause a substantial amount of nonlocal reads that the single-socket server wouldn't have to deal with. That said, that's just the first thing that popped into my head to explain the result. Either way, the resu…

A "single" EPYC is eight 4-core processors so there are even more NUMA effects there.

Re: An EPYC NixOS Build Farm

#15
post #14
post #12

I wonder if there were NUMA effects at play since the Intel server was dual-socket and the EPYC was not. It's not entirely surprising that a CPU-heavy workload reading from filesystem cache (i.e. memory) could cause a substantial amount of nonlocal reads that the single-socket server wouldn't have to deal with. That said, that's just the first thing that popped into my head to explain the result. Either way, the resu…

A "single" EPYC is eight 4-core processors so there are even more NUMA effects there.

I think it’s the other way around: four 8-core processors

Re: An EPYC NixOS Build Farm

#16
post #4
post #2

This is quite surprising. I assumed they would get an EPYC server with higher core at similar price (due to the cost of the CPU) and get advantage in performance/dollar. I didn't expect EPYC to beat a similar physical core count intel server running at similar core count let alone by this much margin. Am I missing something here? I'm saying this as someone who really wants AMD to succeed and push the ecosystem forwar…

The EPYC has twice as many memory busses.

False. The E5-2650 v4 has four memory channels, and with two sockets populated, you get eight memory channels, same as EPYC.

Re: An EPYC NixOS Build Farm

#17
post #14

Earlier quoted context omitted.

A "single" EPYC is eight 4-core processors so there are even more NUMA effects there.

I think it’s the other way around: four 8-core processors

It's four dice with two groups of cores of four each connected by a callosum.

In NUMA-speak, each group is (probably) a node with neighbouring nodes having a lower distance.

Re: An EPYC NixOS Build Farm

#18
post #3
post #2

This is quite surprising. I assumed they would get an EPYC server with higher core at similar price (due to the cost of the CPU) and get advantage in performance/dollar. I didn't expect EPYC to beat a similar physical core count intel server running at similar core count let alone by this much margin. Am I missing something here? I'm saying this as someone who really wants AMD to succeed and push the ecosystem forwar…

EPYC is compared to a previous generation Xeon with lower TDP (105w vs 155/170w) and slower RAM (2400 vs 2666). The Xeon server is more expensive probably because it has 4x the amount of RAM. Edit: actually, this is a dual Xeon machine so its TDP is slightly higher than EPYC's.

> EPYC is compared to a previous generation Xeon with lower TDP ... Edit: actually, this is a dual Xeon machine so its TDP is slightly higher than EPYC's.

Comparing TDPs between manufacturers is invalid.

Re: An EPYC NixOS Build Farm

#19
post #14
post #12

I wonder if there were NUMA effects at play since the Intel server was dual-socket and the EPYC was not. It's not entirely surprising that a CPU-heavy workload reading from filesystem cache (i.e. memory) could cause a substantial amount of nonlocal reads that the single-socket server wouldn't have to deal with. That said, that's just the first thing that popped into my head to explain the result. Either way, the resu…

A "single" EPYC is eight 4-core processors so there are even more NUMA effects there.

We're now well out of my knowledge base, but your comment certainly makes things interesting. If they have similar NUMA latencies (big if!), I guess maybe the edge would go to whichever chip had higher NUMA bandwidth? Just sort of thinking out loud...

Or perhaps it has absolutely nothing to do with memory speeds, but I can't think of what else would have such a dramatic effect. I'd love to see the same test with a single Xeon.

Re: An EPYC NixOS Build Farm

#20
post #3

Earlier quoted context omitted.

EPYC is compared to a previous generation Xeon with lower TDP (105w vs 155/170w) and slower RAM (2400 vs 2666). The Xeon server is more expensive probably because it has 4x the amount of RAM. Edit: actually, this is a dual Xeon machine so its TDP is slightly higher than EPYC's.

> EPYC is compared to a previous generation Xeon with lower TDP ... Edit: actually, this is a dual Xeon machine so its TDP is slightly higher than EPYC's. Comparing TDPs between manufacturers is invalid.

> Comparing TDPs between manufacturers is invalid.

Why? It's all Watts

Post reply on HN