Overclockers Top 6GHz With A 3.6GHz-Rated P4 421
sH4RD writes "The 6GHz barrier has been broken by two guys, a little LN2 (liquid nitrogen for those not as chemistry inclined), and an Intel Pentium 4 (Prescott) 3.60GHz. Check out some icing and some proof of speed. Better yet take a look at how fast it calculates pi. Also be sure to check out the original announcement."
Erm... (Score:5, Insightful)
In all seriousness, this is pretty amazing, but I can't really see the usefulness. For sheer geek pride, sure, why not? But as far as I can tell the expense involved outweighs any gain in performance; for probably half of what these poor folks spent getting a P4 to run stably at 6 ghz (and it doesn't even sound super-stable from what I've read) they could've probably bought a couple more CPUs and had a proper SMP system instead. Regardless, I admire their tenacity and mourn for the warranty on their poor CPU
Tops 6ghz? (Score:5, Insightful)
Re:Erm... (Score:5, Insightful)
Isn't that what being a geek is all about? It's a "becuase it's there"-type of thing.
Re:Erm... (Score:1, Insightful)
Re:Updating Wikipedia Now (Score:2, Insightful)
Cause just about always, people who say that never did a damn progressive thing ever in their life. It's just a lame excuse underacheivers make trying to pull down those who are out there making stuff happen.
Look at yourself first
Re:Cold! (Score:3, Insightful)
It would be amazing to have to use LN2...but then again since I first stuck my finger on top of my 68000 and realising it was a lot hotter than my 6502 i'm constantly amazed how hot these things are getting.
Sure.. that's cool.. what about... (Score:1, Insightful)
Re:Throughput not clock speed (Score:3, Insightful)
when running multi-gigabyte SQL queries (at work, our entire RDBMS is about 1TB), the crawling speeds of the hard drive is evident. the time it takes to develop the SQL query and the time it takes to run it are comparable (btw, the queries are okay optimized)
6GHz might be useful for 3D rendering jobs or obsessive gamers, but for the bulk of the business world, the HDD is still the pain in the a**
This is the type of thing..... (Score:3, Insightful)
Re:6 GHz is not that impressive. (Score:2, Insightful)
also, the P4 excels only in programs so small it can fit in the really small L1 cache. AMD's L1 cache is the really juicy one. =)
Intel designed the Pentium 4 solely around marketing's requirements of consumer hype instead of sound technical choices.
Re:Yksi Kaksi Kolme (or however you spell it) (Score:1, Insightful)
Laskenta=Calculation
Alkaa=To begin, He/she/it begins
Airport has nothing to do with it.
Airport=Lentoasema
Lento=Flight
Asema=Stat
So in a way Airport in Finnish is "Flight station"
So now you know
Re:6 GHz is not that impressive. (Score:2, Insightful)
So long as some effective pre-fetching is in place, there's going to be some asymmetric performance gains. It won't be 1:1 since the memory isn't actually getting any faster, but it doesn't matter so long as the data is where it needs to be when it's needed. In any case, the fact is having the CPU far outstrip the performance of the rest of the system isn't a particularly unusual occurrence.
Re:This is the type of thing..... (Score:5, Insightful)
The "MHz Myth" referrs to the fact that MHz is a poor metric to compare CPUs with. It's fair to compare a 3.2GHz P4 Prescott to a 3.6GHz P4 Prescott and expect that the 3.6GHz chip will be faster. What doesn't make sense is to comare a 3GHz P4 to a 2.4GHz Opteron and claim that the P4 is faster.
You silly mods... (Score:1, Insightful)
When the child post reiterates the caveat of the parent post it's not insightful, it's redundant!
Re:Hang one outside the ISS !! (Score:3, Insightful)
Re:Don't forget the dual clocked ALU (Score:3, Insightful)
Re:calculate pi... (Score:3, Insightful)
Stuart
Re:Erm... (Score:3, Insightful)
Let's assume, for the sake of argument, that main memory is 10 times slower than the slower cache, and that half the cache size means twice as many cache misses (the real figures are actually worse than this, but I don't know what they are exactly).
So, we have:
Main memory access time: 20 units
Small cache access time: 1 unit
Large cache access time: 2 units
Over the course of 100 memory access, lets say 10 of these are misses with the large cache, and based on our assumptions above 20 are misses with the small cache.
Small cache total time: 20*20 + 80*1 = 480
Large cache total time: 10*20 + 90*2 = 380
So, in this situation the large slow cache clearly performs better. In other situations, you might be able to make the small fast cache perform better (e.g. lower number of cache misses, presumably due to applications with smaller working set sizes, or faster main memory might help here).