Overclocked Radeon Card Breaks 1 GHz
dacaldar writes "According to Yahoo Finance, noted Finnish over-clockers Sampsa Kurri and Ville Suvanto have made world history by over-clocking a graphics processor to engine clock levels above 1 GHz. The record was set on the recently-announced Radeon® X1800 XT graphics processor from ATI Technologies Inc."
Graphic showing 3DMark score of 12419:
http://www.muropaketti.com/3dmark/r520/12419.png
Pictures of their setup/methods:
http://www.muropaketti.com/3dmark/r520/ghz/
Things you think are in the Constitution, but are not.
Go here for several examples of this -- far from simply having been proposed, it's been done a fair number of times.
The thing to keep in mind with this is that while the GPU has a lot of bandwidth and throughput, most of that is due to a high degree of parallelism. Obviously 1 GHz hasn't been a major milestone for CPUs for quite a while, but CPUs are only recently starting to do multi-core processing, while GPUs have been doing fairly seriously parallel processing for quite a while.
Along with that, the GPU has a major advantage for some tasks in having hardware support for some relatively complex operations that require a fair amount of programming on the CPU (e.g. multiplying, inverting, etc., small vectors, typically has a single instruction to find Euclidean distance between two 3D points, etc.)
That means the GPU can be quite a bit faster for some things, but it's a long ways from a panacea -- you can get spectacular results applying a single mathematical transformation to a large matrix, but if you have a process that's mostly serial in nature, it'll probably be substantially slower than on the CPU.
Along with that, development for the GPU is generally somewhat difficult compared to development on the CPU. Writing the code itself isn't too bad, as there are decent IDEs (e.g ATI's RenderMonkey) but you're working in a strange (though somewhat C-like) language. Much worse is essentially a complete lack of debugging support. Along with that, you have to take the target GPU into account in the code (to some extent). I just got a call in the middle of a meeting this morning from one of my co-workers, pointing out that some of my code works perfectly on my own machine, but not at all on any his. I haven't had a chance to figure out what's wrong yet, but I'm betting it stems from the difference in graphics controllers (my machine has an nVidia board but his has Intel "Extreme" (ly slow) graphics).
--
The universe is a figment of its own imagination.
The universe is a figment of its own imagination.
...the pictures of the rig : here they are, 3DMark05 included.
in other words... still impressive (no other chip has been able to overclock to 1ghz, even in 2d mode) but not quite what you were hoping for
watch "the money masters" on google video
http://www.xtremesystems.org/forums/showthread.php ?p=1104977#post1104977
sampsa is asked
Were you able to run any benchmarks at that speed or was that a Windows stable shot???? Anyway that is still hella fast with no artifacts.
sampsa's response
Just a Windows shot in 2D.
so still impressive, but not what they describe