Found 3 comments on HN
tcoppi · 2016-08-18 · Original thread
A computer architecture class. For books, [1] is what you will probably use in any decent computer architecture class, and [2] is a good read from a more general audience perspective, if a bit dated.



castell · 2014-08-12 · Original thread
So true. Jon Stokes also wrote the great book "Inside the Machine: An Illustrated Introduction to Microprocessors and Computer Architecture" while he worked at Ars Technica. I have it still in my bookshelf.
frik · 2014-04-28 · Original thread
Higher clock speed, more instructions per cycle and good pipelining architecture means higher single-core raw performance.

We had already complex pipelining superscalar architecture with Pentium Pro and Pentium 4 (Netburst/Prescott). The current Core Architecture has a lot simpler pipelining based on Pentium 3/M. (see )

I favor a high single-core over a slow many-core CPUs.

Have you ever coded a many-core application that runs on thousands of CPUs? I have done using it using , (and CUDA and OpenCL on GPU), as well as traditional using operating system process and threads.

You need new algorithms that work on massive parallel computers. Converting algorithms from serial to massive parallel is possible in many cases, but really hard science work (have done it).

Nevertheless, for a specific domain I would need a really high speed single-core CPU.

A good book about the topic is "Inside the Machine" from ArsTechnica: ...and various university lectures.

Get dozens of book recommendations delivered straight to your inbox every Thursday.