Intel's Quad Core CPU Reviewed
Gr8Apes is one of many to let us know that Tom's Hardware Guide has posted a review of Intel's new Kentsfield quad core processor. From the article: "Even expert opinions are deeply divided, ranging from 'more cores are absolutely necessary' to 'why do I need something more than my five-year-old PC system?' Although the Core 2 quad-core processors are not expected to hit retail channels before October, Tom's Hardware Guide had the opportunity to examine several Core 2 Quadro models in the test labs. We would like to make it clear that these samples were not provided by Intel."
Some applications will make use of it, some won't. More cores is pretty much the same as more CPUs.
Even expert opinions are deeply divided, ranging from 'more cores are absolutely necessary' to 'why do I need something more than my five-year-old PC system?
These are obviously experts who have never heard of servers.
I'm perfectly content with my 1.2GHz single-core single-processor laptop, but I'd sure as shit like to have more muscle in the database cluster I'm responsible for maintaining at work. Whether these chips are a good solution remains to be seen, but that's a separate question.
Proud member of the Weirdo-American community.
At any point of time in the history of computer performance, to say that, "it is stupid *anything*!" is much too simplistic point of view IMHO.
Osho
Some nice example where more processing power (even in parralel) is nice is virtualisation, whether at home or on servers. Running multiple OSes in parallel will saturate all your processing power nicely. :D) gaming platform is now multi-core.
What's more quad-core surely gives more processing power per watt and per cubic meter which is a very important factor for big folks like Google or whereever hosting space is expensive.
Even John Carmack who used to be very much against multi-cores for gamins recently elaborated much on this area in his keynote. Practically any modern (lets call it nextgen
So I'd say overall it's nice that Intel is pushing this so fast, if developers start to realize that multi-cores are hitting mainstream, they will have to take that into account and by the time Intel and AMD launch 8-cores, there should be more software to take advantage of it.
how many FPS can I get in quakeworld? With the +1000 FPS it would give, i'm sure I would be able to bunnyhop all the way across the 2fort5 outdoors area!
260 Watts! We've been looking at the wrong factors - it appears that global warming is related to Moore's law.
Based on Intel's recent naming conventions, I think they'll call it the "Core 2 Duo Duo", so as to generate as much confusion as possible
I don't care if it's 90,000 hectares. That lake was not my doing.
No, that's much to straight forward for Intel.
I expect something along the lines of: "Core 2 Tre Quad Pentium 405".
And AMD's AM3 5235+ 3.1G X4 Thunderon is faster and cheaper, anyhow.
Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
There's an ad for PC World or Currys or something where the salesguy explains to some students that having an Intel (bing-bong-bing-bong) dual core processor means it can do two things at once - like sending an email and downloading music!
As a sofware developer, I can't help but think the move to multiple cores is a good thing. In my mind, anything that makes software development MORE complex can only improve my employability.
They should have made the FSB 4 Mhz faster. That'd just be too cool. Fight back AMD! Don't take that shit!
Is Linux Kernel compilation. It should rock there, that's an inherently parallelizable task.
:)
As a programmer, I want one. No, I want two
"Well, they've had twin-core - let's give them FOUR cores! And an extra one on the back!"
"It's... it's brilliant!"
Yes, Intel are the new Gillette. ;-)
Meta will eat itself
Why is it so hard to get developers to write decent multi-threaded code? It's not that hard,
Let me put it this way. If all the developers in the world were as smart as you think you are, it would not be that hard. As it is, however, coming up with scalable, manageable, efficient ways of writing multi-threaded code, in a way that is future-proof, as opposed to simply optimized for todays generation of hardware, is hard. Very hard. Not as in research-subject hard, but as in continuing-research-for decades-has-still-not-brought-us-much-closer-to-a- solution hard!
, and using threads properly can almost always improve performance and/or responsiveness on single proc/core machines to boot.
Let me rephrase part of the above sentence: "using threads properly can...". Did you notice which word I emphasized? Can you guess why?
Any idiot can use threads. The difficulty is to find the right granularity of threads (which is related to what kind of hardware you've got), which tasks are parallelizable, which parallelizable tasks should (or should not) get parallelized because of communication overhead and other factors (which is also related to what kind of hardware you've got), and so on.
It is also important to note, that few existing programs are designed from scratch today. In fact, almost all existing programs were designed in the past! In the past they didn't have affordable multicore (or multi-CPU) computers. And thus, those old designs didn't take that into account.
Why is it so hard to get developers to write decent multi-threaded code? It's not that hard, and using threads properly can almost always improve performance and/or responsiveness on single proc/core machines to boot.
Because it IS harder. It introduces new pitfalls (deadlocks, livelocks, race conditions), debugging is harder (gdb with multithreaded programs.. brrr), old paradigma have to be thrown overboard (and new ones introduced, such as task- or stream-based processing). Also, threads NEVER improve performance on a single-core machine. They do help with responsiveness, however. If you want performance boosts, use a multicore machine.
This sig does not contain any SCO code.
I grew up programming transputer clusters cos I figured Moore's law wqould have to slow down sometime and then we would have to move to multiprocessor systems. Efficiently using more than a couple of cores is *not* easy.. and it opens up a whole realm of interesting algorithmic work where basic problems with established solutions suddenly become open again.
Its about fucking time...
http://rareformnewmedia.com/