News for hackers. Stuff that matters.
Re:It's all about the cores. Why AMD doesn't use HyperThreading by jacquesm on Thursday January 21, 2010 @06:01PM (#1068607)
> Running more threads increases throughput for applications as long as you have available cores.

As long as you are CPU bound.

Once you're IO bound you can have as many cores as you want but it isn't going to move any faster.

The only machines where I manage to approach 100% cpu usage are video servers, all the other boxes are sooner or later IO bound. The only cure for that is gobs of memory.

It's in my experience pretty rare to have a webserver with more than 4 cores to be CPU bound. Most of the time the disk or the network card are the bottle-neck.

Unless you code in a very inefficient way of course, then it can be that you need more CPU before you hit that wall.

AMD so far more or less held the moral high ground against intel in the 'spin wars', they can do better than this.

It's simply a marketing piece in the guise of a blog post.

At the bottom of the entry it reads:

> John Fruehe is the Director of Product Marketing for Server/Workstation products at AMD. His postings are his own opinions and may not represent AMD’s positions, strategies or opinions.

So they effectively distantiate themselves from this posting but at the same time it sits on amd.com.

Re:It's all about the cores. Why AMD doesn't use HyperThreading by JF-AMD on Friday January 22, 2010 @09:46PM (#1071260)
Ah, welcome to the world of lawyers. Those disclaimers are everywhere, like the the labels on the lawnmowers that say "don't pick this up while it is running." They aren't distancing themselves from me, just standard legal stuff.

Yes, it is marketing, but my job is marketing.

You are definitely right that CPU is not always the problem, some systems can be I/O or memory-bound.

Our 4 channels of memory on the new products will help with the latter; to fix the former, you need OEMs willing to put down mulitple chipsets. Typically the cost drives people away from those designs, unfortunately.