Live data from Hacker News

AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

anandtech.com

81–90 of 169 posts

Re: AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

#81
post #25

Earlier quoted context omitted.

Outside of some very exotic scenarios you are IOPS bound on writes and not CPU bound.

Is that still a problem with cheap NVMe drives that can do 500k IOPS?

Nope but everyone is running in the "cloud" and there you are lucky to get 50K IOPS

Re: AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

#82

Earlier quoted context omitted.

Let's hope this isn't niagra again: it needs to have decent clock speeds as IPC is still worth something today. But yes, I totally agree, this is an exciting chip.

It's not, not only did AMD move from CMT (clustered multi-thread) design used in the previous Bulldozer microarchitecture, they now have an SMT (simultaneous multithreading) architecture allowing for 2 threads per core. By comparison, the performance of sparc substantially improved moving from the T1, T2 to T3+. The T1 used a round-robin policy to issue instructions from the next active thread each cycle, supporting…

I didn't know about this. Are there benchmarks that aren't canned by Oracle that you know of? I'm intrigued by this round-robin way of threading. I'm not a cpu expert, but how does this compare with the Power arch's way of threading?

Re: AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

#83

Earlier quoted context omitted.

It's quite rare to find GPUs being used in genetics.

Is that because the workloads are fundamentally unsuitable for current GPU architectures or because no one has took a good stab at it yet? I know very little about computation genetics/biology but it sounds interesting.

I don't think it is because no one has tried it as much as the fact that the workloads need the cpu architecture / are not easily parallizable (as far as I understand). Comp bio in genetics is largely sequence alignment & search, which is still largely CPU / memory bound; but I don't understand programming enough to speculate if development in algorithms will allow GPUs to be used because the problem itself is not parallelizable. I think of it as the difference between a super computer & a cluster..

(More than a decade ago, I struggled to / barely succeeded in building a Beowulf cluster; I am just amazed at how far both the hardware & the software tools have come..)

In other areas of comp bio though, GPUs I think are finding use. Protein folding, molecular dynamics. Also, with STORM & such: super resolution microscopy? I think increasingly, gpus will become important.

Also, whole cell simulations?

Re: AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

#84

I think Naples is a very exciting development, because: - 1S/2S is obviously where the pie is. Few servers are 4S. - 8 DDR4 channels per socket is twice the memory bandwidth of 2011, and still more than LGA-36712312whateverthenumberwas - First x86 server platform with SHA1/2 acceleration - 128 PCIe lanes in a 1S system is unprecedented All in all Naples seems like a very interesting platform for throughput-intensive…

> 8 DDR4 channels per socket is twice the memory bandwidth of 2011, and still more than LGA-36712312whateverthenumberwas

This one will be interesting. The current Ryzen (like most of the Intel desktop range) has two channels, but everyone has been benchmarking it against the i7-6900K because they both have eight cores. The i7-6900K is the workstation LGA 2011 with four channels. If the workstation Ryzen will have eight channels...

Re: AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

#85

With how big these chips are getting, I wonder if the next iteration will have an HBM last-level cache on chip.

That's the old EHP concept.

http://wccftech.com/amd-exascale-heterogeneous-processor-ehp...

I'd like to have that in the old project quantum package: http://wccftech.com/amd-project-quantum-not-dead-zen-cpu-veg...

That would be a TFLOPS level supercomputer on your desk.

Re: AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

#86

I think Naples is a very exciting development, because: - 1S/2S is obviously where the pie is. Few servers are 4S. - 8 DDR4 channels per socket is twice the memory bandwidth of 2011, and still more than LGA-36712312whateverthenumberwas - First x86 server platform with SHA1/2 acceleration - 128 PCIe lanes in a 1S system is unprecedented All in all Naples seems like a very interesting platform for throughput-intensive…

My shallow understanding of big servers and IBM Z series amounted to "lots of dedicated IO processors". Seems like "mainstream" caught up with big blue.

Re: AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

#87
post #47

Earlier quoted context omitted.

>And AMD should dump SHA1 acceleration in the next generation. The cost to have that on silicon is probably close to zero. If you think SHA1 is just going to magically disappear because you want it to, well, you'll be in for a SHA1 sized surprise. Our grandkids will still have SHA1 acceleration. >ARMv8 has had it for like 2-3 years now... Because ARM cores don't remotely have the CPU heft an Intel x86/64 chip has, so…

Why should it be dropped ? Isn't it just a hash function ?

If you remove things from the instruction set, any code that uses them will either crash or run very slowly in emulation.

Most uses of special instructions will check feature bits or CPU version, but not all will do so correctly.

(I'd say that the additional area cost of something like this is small, and the big cost of special instructions is reserving opcodes and feature bits)

Re: AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

#88

Earlier quoted context omitted.

It's quite rare to find GPUs being used in genetics.

Is that because the workloads are fundamentally unsuitable for current GPU architectures or because no one has took a good stab at it yet? I know very little about computation genetics/biology but it sounds interesting.

AFAIK probably a bit of both. A majority of genetics/biology workloads are I/O bound (mapping, blast, etc) and/or require a lot of memory (i.e. de novo assembly of genome)

On the other hand many of the bioinformatics software solve a specific scientific question and usually are written by people with mostly non-computational background. They use higher level languages such as Python/Perl/R and people often don't have the expertise or time to implement them for GPUs.

However now that machine learning and deep neural network approaches are being picked up by the field, the workloads might change a and also there are frameworks that make it easer to leverage GPUs (Tensorflow, etc)

Re: AMD Prepares 32-Core Naples CPUs for 1P and 2P Servers: Coming in Q2

#89

Earlier quoted context omitted.

Is that because the workloads are fundamentally unsuitable for current GPU architectures or because no one has took a good stab at it yet? I know very little about computation genetics/biology but it sounds interesting.

I don't think it is because no one has tried it as much as the fact that the workloads need the cpu architecture / are not easily parallizable (as far as I understand). Comp bio in genetics is largely sequence alignment & search, which is still largely CPU / memory bound; but I don't understand programming enough to speculate if development in algorithms will allow GPUs to be used because the problem itself is not pa…

What you wrote about super computer vs cluster is quite right. Recently I attended a HPC meeting where we were the only DevOps of an HPC for a biological institute and most of the other people were from physics & chemistry. They usually don't consider the biology workloads as High Performance Computing but as big resource/data computing. The physics & chemistry guys run simulation using hundred thousands of cores and are mostly CPU bound. They use MPI and their nodes typically have not more than 64 GB and they consider 120 GB memory usage as a lot. Biologist on the other hand hardly use MPI because they can just parallelize the workload on the data level (i.e. sample or chromosome) and run them independently on each node. For that reason also high memory NUMA machines from SGI can relatively often be found.

You are also right that some of the comp bio areas (CryoEM, protein folding, molecular dynamics) are well suited for GPUs

Post reply on HN