3 ms·
Enormous, but extremely specialized power. I'm not sure if most people understand the kinds of threads/cores that GPUs actually have, and with that, the kinds
by scott_s 17y ago
Enormous, but extremely specialized power.
I'm not sure if most people understand the kinds of threads/cores that GPUs actually have, and with that, the kinds of computations they're actually good at. A GPU's threads are extremely simple execution pipelines - nothing like the cores of an Intel Quad Core chip. Groups of GPU threads actually execute together in lock-step, executing the same code (but with different parameters).
Such devices are extremely good at handling data parallelism - where the same computation is performed on a large chunk of data - seen in areas such as graphics and scientific computing. But you're probably not going to, say, speed up your webserver with a GPU. If you don't have a computation that is extremely data parallel - that is, capable of having thousands of execution contexts working on data at the same time - a GPU won't help.
- jacquesm 17y agoThe model is parallel SIMD, so in other words, multiple banks of cores, within each bank all the cores are doing the same thing at the same time. A GPU won't help with our current programming model, maybe there is room for a new model then ? That won't happen overnight, but one thing is for sure, if you want to get more performance than what your applications are giving you today then you'd better learn how to code for massively parallel systems.
- scott_s 17y agoI'm intimately familiar with the programming model that GPUs use. The difficulty is that only a limited subset of our problems are amenable to it. I think we need something a little less special-purpose than a GPU to be more widely applicable. Certainly, the computing world is going parallel. My personal belief is that what we end up with will be a heterogeneous chip with some parts good at massively parallel computations, and some good at sequential computations. But I think GPUs themselves represent a stop-gap; the communication cost of transferring data off the motherboard to the card is just too high for fine-grained parallelism. Once we have that sort of architecture on-chip the game changes. Intel's Larabee and AMD's Fusion promise to do this. The Cell was close, but making the vector processors completely divorced from the normal memory hierarchy makes programming for them much more difficult. (Although it does give me many research opportunities.)
- jacquesm 17y agoIt sounds like you have an interesting work environment. I agree that GPUs are a stopgap, but they're a pretty interesting one. I've had all kinds of co processors over the years, small clusters, DSP daughter boards, transputers and so on. Nothing to date comes even close to the power of the GPU boards that you can buy right now. The comms cost is indeed where the problems lie, but that can go two ways: 1) a more formalized form of high speed interconnect (such as infiniband directly on the GPU card) 2) a port of a general purpose OS to a GPU. Some people are already working on (2), (1) is probably not in the cards unless somebody orders a very large number of boards. There are motherboards that will hold 4 or even 6 PCI express cards too. I don't have any experience with the cell architecture, I'll go do some reading, it sounded interesting enough when it was released but I never got around to study it. More reading to do I guess :)
- scott_s 17y agoI'm a CS PhD student doing high performance systems research. My dissertation work has focused on Cell, and this summer I'm working with GPUs in an internship. (My profile has a link to my academic page where you can find my Cell related work.) Personally, I think that GPUs as we know them won't be around long enough for 1) or 2). Moving the GPU (or a GPU-like computation accelerator) onto the chip itself changes everything. I think it's also worth keeping in mind that GPUs are, essentially, tiny computers unto themselves. Putting a GPU in a system now is like installing a computer in a computer.
- jacquesm 17y ago> I think it's also worth keeping in mind that GPUs are, essentially, tiny computers unto themselves. Putting a GPU in a system now is like installing a computer in a computer. I've been doing exactly that for the longest time, first with a DSP32, then with a transputer card. Then I switched to small scale clusters (the largest had 10 nodes, see here http://www.clustercompute.com/ http://www.clustercompute.com/ ), now GPUs. Your take on 1) and 2) is noted, thanks for that insight.
- apu 17y agoThings are changing extremely rapidly. Researchers (especially in parallel computing) are already figuring out how to port all sorts of algorithms over to the GPU -- and not just scientific or graphics code -- we're talking general purpose algorithms like sorting, ranking, cryptography, networking, database operations, etc: http://gpgpu.org/2009/04/13/efficient-acceleration-of-asymmetric-cryptography-on-graphics-hardware http://gpgpu.org/2009/04/13/efficient-acceleration-of-asymme... http://gpgpu.org/2009/04/28/fast-and-scalable-list-ranking-on-the-gpu http://gpgpu.org/2009/04/28/fast-and-scalable-list-ranking-o... http://gpgpu.org/2008/12/11/wait-free-programming-for-general-purpose-computations-on-graphics-processors http://gpgpu.org/2008/12/11/wait-free-programming-for-genera... http://gpgpu.org/2008/10/26/gnort-high-performance-network-intrusion-detection-using-graphics-processors http://gpgpu.org/2008/10/26/gnort-high-performance-network-i... http://gpgpu.org/2008/05/25/a-fast-similarity-join-algorithm-using-graphics-processing-units http://gpgpu.org/2008/05/25/a-fast-similarity-join-algorithm... The biggest obstacle to preventing widespread adoption of GPGPU techniques today is that things are still in so much flux that mature, stable APIs have not yet emerged. There is fierce competition between Intel (Larrabee), Apple/AMD (Grand Central/OpenCL), and NVIDIA (CUDA) to get their respective APIs to be the dominant ones, and no one's yet come up with a mature wrapper API that can target any of them. This is in large part because the hardware itself is still in flux, morphing away from the graphics-specific pipeline of 10 years ago and into a general purpose SIMD architecture. This has meant a change in the kinds of operations allowed on the GPU. For example, branches used to be a big no-no in graphics hardware: the performance hit caused by a branch was disastrous on a massively-multicore system. However, all hardware makers are now adding supporting for branches, because it's almost impossible to port a lot of CPU algorithms without them. In any case, I'm confident that within a year or two, things will have settled down somewhat, at which point there's going to be a mad dash by developers to start using GPUs (probably systems- and library-level developers rather than application-programmers).
- jacquesm 17y agoWell, count me in, as far as I'm concerned the mad dash has already begun. I've decided to splurge on the largest CUDA capable card that will fit this machine without blowing up the power supply. Stuff like this is still cutting edge but will be mainstream soon, the time to gain experience is today. Not to wait.