3 ms·
How is it the world's most powerful if its loaded with Nvidia cards? 200 series era Geforce cards were slower per watt and per dollar and per slot (all importa
by DiabloD3 15y ago
How is it the world's most powerful if its loaded with Nvidia cards?
200 series era Geforce cards were slower per watt and per dollar and per slot (all important here) than 58xx series Radeons on both single precision and double precision math (and integer as well, but integer is only useful for crypto and Radeons have native single cycle instructions common for crypto which makes them about 4-5x faster than Geforces, but not a typical use case).
And if we're comparing series 400/500 to 69xx, the beating is much worse.
- risratorn 15y agoProbably because some hasn't yet assembled a similar system with ATI cards? They claim they have the fastest desktop system and it probably is at the time of writing but as far as i can tell they didn't say it couldn't possibly be better/faster. There's always room for improvement no? :)
- sp332 15y agoNvidia and ATI cards have (approximately and with a few exceptions) the same performance per dollar when it comes to 3D graphics applications. But the tradeoffs made internally mean that they have radically different performance in other areas. For example, ATI chips are faster then Nvidia for bitcoin mining (edit: lots of sha256 hashes), but Nvidia is generally faster than ATI at physical modeling. http://ewoah.com/technology/a-very-good-guide-to-building-a-bitcoin-mining-rig-cluster-guide/#Why%20are%20ATI%20GPUs%20better%20than%20Nvidia%20GPUs%20for%20Bitcoin%20mining http://ewoah.com/technology/a-very-good-guide-to-building-a-... http://stackoverflow.com/a/4642578/13652 http://stackoverflow.com/a/4642578/13652 All this is moot if the application they're running only supports CUDA - then they're stuck with Nvidia.
- DiabloD3 15y agoAuthor of DiabloMiner, the worlds most popular GPU miner, here... I think you mean SHA256. If they're stuck on CUDA, I feel sorry for them. They'd be better off rewriting the app to use OpenCL to take advantage of AMD's superior chip design and not be stuck on Nvidia/Windows (Nvidia Linux support, especially under CUDA, is horrible; rather depressing once you consider most CUDA clusters run Linux).
- supar 15y agoCan you give us some thoughts on how (why?) bad is nvidia/linux support is? As a linux developer doing scientific visualization, and having tested (and still testing, btw) how bad still is the AMD driver status on linux, I see basically nvidia as my only choice if I want to get anything done with decent (and stable) performance. I wouldn't run a cluster on anything but .nix, so I really see no alternative on nvidia by my reasoning here, even if nvidia's architecture is actually inferior. But I'd really like to have some opinions on that front. I really want alternatives, and the closed nature of nvidia's drivers is a problem for me. So, can you elaborate? I also programmed on w2k (from around 2001-2004) and I used to target both nvidia and ati, and I still remember the sheer number of bugs I had with GL in general with the radeon drivers. But I cannot really speak anymore on that front.
- DiabloD3 15y agoI have answered most of your question here already: http://news.ycombinator.com/item?id=3337682 http://news.ycombinator.com/item?id=3337682 Nvidia driver quality continues to be subpar on Linux, yet I have zero issues with Catalyst. And even if Catalyst had a problem, as I described in the above URL, AMD is shelling a lot of money out to make the FOSS driver their one and only driver which already is shaping up to be a lot better than Catalyst. I just don't see a point in doing business with a company that is clearly trying to lock me in with closed source vendor specific APIs if they have no interest in supporting me after the sale of the hardware. In addition, their OpenCL implementation (which is shared across both Windows and Linux) seems to run code much slower than it should, which I suspect (but have no way of proving) they are doing it to make CUDA look better. The same code ran on AMD hardware has zero issues, and the equivalent code in CUDA runs about as fast as I think it should. And also, re: Catalyst vs FOSS, in about 2 years the Mesa/Gallium OpenCL stack should be finished, so not only will I be able to quit using Catalyst altogether, Nvidia users will be able to make the better use of their hardware and ditch the broken drivers Nvidia keeps forcing on people. Now, who knows, maybe Nvidia will change tactics and quit screwing over customers and developers, and release the programming manuals for their hardware so FOSS can develop a better driver faster... I just don't see it _ever_ happening. Even if AMD hardware had a higher total cost of ownership, the fact AMD actually cares about me as a Linux customer is why for the past 5 video cards I've owned they have gotten my business. re: Your programming experience, 2004 predates AMD taking over ATI. Driver quality pre-AMD was worse than Nvidia was at the time, but it has greatly changed. AMD has vastly increased the quality of the Windows driver, and the original Linux driver was thrown out in exchange for one that shares almost all the code with the Windows one (day and night kind of change in quality). AMD didnt finalize their purchase of ATI until 2006, and it wasn't until 2007 or 2008 that driver quality started taking off. As a statement of driver quality, people who use my software regularly report 30+ day uptimes using Catalyst on Linux. If it was so buggy and unstable, this would probably be impossible.
- vilya 15y agoBecause no-ones bothered to build one using the ATI cards, maybe? I would guess the main attraction of Nvidia cards was probably CUDA, which is still a nicer environment to program for than OpenCL and seems to have a more lively ecosystem of libraries, tools, etc. Also, floating point & integer math aren't the only relevant performance metrics. For their application domain, memory bandwidth & latency would probably be at least as important. Kernel switching time may be a factor too - there are many things you can't do with a single kernel. I don't know (but would be interested to hear) how the cards stack up against each other in those terms.
- DiabloD3 15y agoI'm not sure how you can claim CUDA is nicer. CUDA is not a public specification, it has poor documentation, and it only works on Nvidia. I am a software engineer (or whatever the popular term this week is) who uses OpenCL frequently. I couldn't imagine being stuck on something like CUDA, between the C++ obsession and the fact it follows Nvidia Cg's way of syntax design instead of GLSL (OpenGL Shader Language) makes it difficult to use. In addition, there never will be a native Linux implementation that is open source as Nvidia has basically tried to screw over Mesa/Gallium repeatedly with vague IP rights threats (see also, Nouveau, the X/Gallium driver for Nvidia cards, and how they unofficially threatened to sue if Nouveau continued reverse engineering hardware interfaces; they backpedaled when it got media coverage). So, I dunno about you, but I don't like depending on companies that continuously screw developers who made the mistake of supporting their hardware. OTOH, AMD has paid over $2 million in their open source efforts including having their legal department clear the programming manuals for use by X/Mesa/Gallium and also hiring multiple full time developers to work on the open source drivers, and has clearly supported FOSS at every turn.
- sausagefeet 15y agoCan you speak to Microsoft's AMP framework at all? I believe AMD has stated they will support it.
- DiabloD3 15y ago
- microarchitect 15y agoWhen I was working for AMD, I heard from the GPU guys that one of big the reasons they weren't seeing a lot of HPC-space adoption for the Radeons was because they didn't (yet) support ECC for the DRAM.
- ansgri 15y agoA bit offtopic, but we of image processing do use integers a lot: they're fast, single SSE instruction processing whole 16 uint8s at once.
- DiabloD3 15y agoExcept video cards do image processing every single day. Modern game engines use floating point pipelines the whole way through, the only integers in the GPU typically being texture data and the final output to the screen. SSE2 integer usage may be fast, but GPUs are faster, typically by several magnitudes.