First Look At Intel Tejas & Socket 775
Anonymous Indian writes "The snoops at Anandtech have unearthed some details and photos of Intel's rumored Tejas 90nm CPU which draws 150 watts of power, a 50% jump compared to Prescott. It's also got an interesting locking mechanism instead of the traditional metal clip from hell for most processors." There's not much info beyond the photos, but it's still interesting to see what lies ahead for Intel.
The both the slashdot sum-up and the linked article fail to explain why, exactly, I should be excited about this.
The only trouble is that power usage inside computers is skyrocketing lately.
150 Watts CPU, a 100 Watts graphics card and then you have all the fans to cool it, and you'll be lucky if you are under 300W and that doesn't even factor in storage, optical drives, motherboard, audio, communication devices.
I mean you will need a hell of a power supply unit to provide that sort of power reliably.
IntechHosting - Free domain, 2GB, PHP, £4.95/$8.95
You only seem to equate power wastage in terms of your personal $s.
Try and think a little bit bigger. Think in terms of global warming, energy depletion, entropy etc.
Using less power (whatever the application) can only be a good thing.
Mod parent as troll.
Why should it be modded as a 'troll'? just because it betrayed some lack of knowledge about CPU design? I think your post should be modded as troll.
autopr0n is like, down and stuff.
From my description of SMT, you might conclude that it is able to make the fullest use of CPU core resources of any multithreading approach. Then why are some benchmarks slower with HyperThreading enabled? I have three ideas. First of all, since OSes tend to treat a single CPU with hyperthreading like a dual-CPU system, they may schedule lower-priority processes on one of the threads, resulting in less total CPU time available for the main benchmark process. Secondly, there is some overhead to multiplexing all of these resources amongst two threads, so perhaps Intel had to "tone down" superscalar operation or memory queues to meet clock timing when in HyperThreading mode (I know this is vague). Thirdly, perhaps in ostensibly non-HyperThreaded mode the second thread is actually used for speculative execution, and hence slightly boosts the performance of a benchmark.