Talk:General-purpose computing on graphics processing units

message: Updated the page to include a basic overview of GPGPU - history and techniques, as well as some more applications.  More detail could be added to all the techniques, and the data structures need to be expanded.  Applications could also be added and more detail about important/common ones could be added.
Echeslack 19:01, 13 December 2005 (UTC)
thread_title:  Updated 

message: 8 bits per pixel - Palette mode, where each value is an index into a table with the real color value specified in one of the other formats. Possibly 2 bits for red, 3 bits for green, and 3 bits for blue.
this bit allocation does not make sense for pallete mode. Should we remove that phrase?
--Diego 14:38, 13 June 2006 (UTC)
replies: text: I'd also contest that the bit allocation is inaccurate. Given the sensitivity of the human eye to different colours, it's far more likely that any fixed bit-per-channel allocation would be 3-3-2, with blue only having 4 levels (2 bits) and the other two components having 8. Though in practice, isn't a 216 colour evenly-spread "web safe"-type scheme (6 levels per channel with no direct correlation between channels and bits) more common in the fairly rare examples of a 3D accelerator outputting in less than 15 bpp but not using a completely custom (eg as found in Quake et al) palette? 193.63.174.211 (talk) 13:37, 11 January 2012 (UTC)
thread_title:  Data types 

message: what about creating a section containing OpenGL Shading Language and related?
: There's a page on shading languages which would need some work. I think it would be better to put the thing there.
:MaxDZ8 talk 21:53, 13 June 2006 (UTC)
replies: text: Well, gpgpu have been using glsl much more than hlsl, so it's a bit strange that it isn't mentioned at all.  —Preceding unsigned comment added by 128.39.210.208 (talk) 12:32, 23 April 2010 (UTC)
thread_title:  Languages 

message: "The programmability of the pipelines have trended according the Microsoft’s DirectX specification, with DirectX8 introducing Shader Model 1.1, DirectX8.1 Pixel Shader Models 1.2, 1.3 and 1.4, and DirectX9 defining Shader Model 2.x and 3.0. "
This sentence make no sense what so ever, 'trended' is a strange verb to use here (or indeed anywhere) and the rest is non grammatical anyhow. Did the author want to say something like "have followed the DirectX specification?".
how does this all relate to OpenCL etc - the article seems overly full of references to Microsoft's DirectX when there are other competing technologies out there.
Long story short: CL is the newcomer to all of this and there's no chance (or very little chance) to rephrase the above without referencing to D3D or some DirectX ecosystem. Direct3D is the only API I know with clear and (often) explicit definition of the concepts referred in the above statements. Writing the same in terms of OpenGL would be possible but extremely verbose in the best case and just plain out impossible in some other cases (such as single-float blending, of which GL had no notion at all last time I checked). When it comes to OpenCL the situation is slightly better (I have been told so) but in the end, its approach it's very similar to GL and has no chance to scale back to anything that is not at least Shader Model 4 (maybe 3) in functionality.  — Preceding unsigned comment added by MaxDZ8 (talk • contribs) 14:37, 25 July 2011 (UTC)
replies: text: What I take from that phrase is that graphics chip / card manufacturers have concentrated on adding features to their GPUs - both those useful for GLGPU, and for "normal" graphics - that move them further up the DirectX version ladder, sometimes at the expense of the features which don't. It improves both their saleability, compatibility and longevity. So to get an idea of what features next years' GPUs may have, take a look at Microsoft's DirectX roadmap... 193.63.174.211 (talk) 13:40, 11 January 2012 (UTC)
thread_title:  Programmability 

message: I'm brand new to GPGPU, but I think frameworks such as Lib Sh, BrookGPU and the Microsoft Research Accelerator Project should be mentioned somehow... —Disavian (talk/contribs) 17:07, 27 October 2006 (UTC)
thread_title:  APIs 

message: I disagree with the move proposal; GPGPU is more than just a subset of stream processing. Also, the stream processing article is too long, and should probably have pages broken out of it, instead of having more content merged into it. —Disavian (talk/contribs) 01:57, 6 November 2006 (UTC)
thread_title:  Move 

message: The phrase in the intro "a recent trend in computer science": it's not really anything at all new in computer science at all, is it? Much more computer engineering. Though not just software engineering. (Though "computer science" itself is closer to engineering than science a lot of the time.) The Computer engineering article is about hardware engineering and I suspect wouldn't be the right term to put in the intro. Computer programming isn't the perfect choice either. Ideas? - David Gerard 09:47, 7 September 2007 (UTC)
thread_title:  "a recent trend in computer science" 

message: Is there a suitable image for this article? A photo, some block diagrams? I just thought it could do with some decoration :-) - David Gerard 09:49, 7 September 2007 (UTC)
thread_title:  Suitable decoration? 

message: This article is definitely remiss for not mentioning or linking to NVIDIA Tesla Raul654 05:44, 6 November 2007 (UTC)
thread_title: Missing link

message: A few questions that I was left wondering after reading the article:
# Is code written for CPU processors (eg i386) easily ported to GPUs or is major redesign necessary. (CPU->GPU)
# Is code written for one GPU portable to another? (GPU1->GPU2)
# Are there any GPU programming standards?
Pgr94 11:21, 14 November 2007 (UTC)
thread_title:  Software portability 

message: The article says it is important for applications to have high arithmetic intensity - does this mean that non-arithmetic applications are not well-suited to GPGPU's? Pgr94 11:25, 14 November 2007 (UTC)
thread_title:  Only interesting for floating-point / arithmetic applications? 

message: All this text, and not a single mention of OpenGL Shading Language?  Insensitive Clods! -Anonymous Coward  —Preceding unsigned comment added by 65.24.75.114 (talk) 04:45, 5 February 2008 (UTC)
thread_title:  GL Shader 

message: Removed a vague mention in the introduction of a (technically questionable) connection with real-time computing. Neither article expands on this connection. If it's legitimate, it should be explained in the body of the article. Bryan Silverthorn (talk) 14:41, 30 March 2008 (UTC)
thread_title:  Real-time 

message: A proposed deletion template has been added to the article Lib Sh, suggesting that it be deleted according to the proposed deletion process. All contributions are appreciated, but this article may not satisfy Wikipedia's criteria for inclusion, and the deletion notice should explain why (see also "What Wikipedia is not" and Wikipedia's deletion policy).  You may prevent the proposed deletion by removing the  notice, but please explain why you disagree with the proposed deletion in your edit summary or on its talk page.
Please consider improving the article to address the issues raised because even though removing the deletion notice will prevent deletion through the proposed deletion process, the article may still be deleted if it matches any of the speedy deletion criteria or it can be sent to Articles for Deletion, where it may be deleted if consensus to delete is reached.  Do you want to opt out of receiving this notice? —Disavian (talk/contribs) 21:15, 10 June 2008 (UTC)
thread_title: Proposed deletion of [[Lib Sh]]

message: It seems to me that Digital image processing, Video Processing, Raytracing, Global illumination and Geometric computing all fall under the normal use of a graphics processing unit and thus do not qualify to be listed on this articles' page as general purpose computing applications.  I suggest that they be removed from the list.
Bkessler (talk) 02:32, 28 July 2008 (UTC)
thread_title:  Graphics Specific Applications 

message: Given that people go to the effort of implementing algorithms on a GPU are doing so because of potential speed improvements some comments on the relative performance level of specific algorithms. -- for example the folowing evaluation showing up to 30x speedup for large problems (the paper concludes that the large problem is still limited by overheads).
Intel Core 2 Duo E6750 Vs GeForce GTX 280 (G200 chip).http://www.mathematik.tu-dortmund.de/~goeddeke/pubs/GTX280_mixedprecision.html
Number of variables	Mflops on Intel Core 2 Duo E6750	Mflops on Nvidia GTX 280	speedup
16, 641            	1405                            	2788                    	2.3x
66, 049            	1114                            	8086                    	7.8x
263, 169           	886                             	15179                   	17.4x
1, 050, 625        	805                             	21406                   	26.9x
They also estimate performance per watt improvements of 11.5 and performance per euro increase of about 16.
For other applications speedups of >60 have been reportedhttp://www.citeulike.org/user/bwking/article/3008417.
Andy t roo (talk) 01:27, 16 September 2008 (UTC)
thread_title:  Relative performance 

message: The Kappa Library is missing from "GPU programming libraries/layers".  It is an object-oriented Producer/Consumer scheduler library on top of CUDA and OpenMP from Psi Lambda LLC (my company--full disclosure).
----  —Preceding unsigned comment added by Psilambda (talk • contribs) 20:20, 8 July 2010 (UTC)
thread_title:  GPU programming libraries/layers section is missing the Kappa Library 

message: If you disassemble a typical cpu program you get a list of cpu opcodes starting from an entry point such as a main() function. What exactly happens when the program wants to transfer to the gpu (whether stored in the program itself or a library like a DLL)? I think this is important to add to the article but i can't find it elsewhere on WP.  —Preceding unsigned comment added by 58.152.239.68 (talk) 07:34, 1 August 2010 (UTC)
thread_title:  binary format 

message: I'm new to editing wiki pages and not sure how to fix this so I'm mentioning it here until I can figure it out or someone else does it.
Ref 22 has dead/broken link.  — Preceding unsigned comment added by Abdd0e77 (talk • contribs) 14:58, 28 May 2013 (UTC)
thread_title:  Ref 22 has dead link 

message: I just removed this from the lede:
:Any GPU providing a functionally complete set of operations performed on arbitrary bits can compute any computable value.
For a suitable definition of "computable value" (and some stretching of the notion of functional completeness), this is a tautology. It's not saying anything about GPUs. QVVERTYVS (hm?) 11:50, 25 August 2014 (UTC)
thread_title:  Computing any computable value 

message: Hello fellow Wikipedians,
I have just added archive links to  on General-purpose computing on graphics processing units. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive https://web.archive.org/20130616205308/http://openhmpp.org/ to http://www.openhmpp.org/
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
Cheers.—cyberbot IITalk to my owner:Online 23:35, 11 February 2016 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified one external link on General-purpose computing on graphics processing units. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20100927155948/http://www.hpcwire.com/features/MATLAB-Adds-GPGPU-Support-103307084.html to http://www.hpcwire.com/features/MATLAB-Adds-GPGPU-Support-103307084.html
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 18:01, 9 September 2017 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified 3 external links on General-purpose computing on graphics processing units. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20111101184143/http://www.clusterchimps.org/ocltools.html to http://www.clusterchimps.org/ocltools.html
*Added archive https://web.archive.org/web/20051129010626/http://www.gpgpu.org/w/index.php/Main_Page to http://www.gpgpu.org/w/index.php/Main_Page
*Added archive https://web.archive.org/web/20091223141933/http://developer.amd.com/GPU/Pages/default.aspx to http://developer.amd.com/GPU/Pages/default.aspx
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 12:39, 12 October 2017 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified one external link on General-purpose computing on graphics processing units. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added  tag to http://www.futurechips.org/tips-for-power-coders/basic-technique-to-help-branch-prediction.html
*Added archive https://web.archive.org/web/20111105120646/http://www.futurechips.org/chip-design-for-all/cpu-vs-gpgpu.html to http://www.futurechips.org/chip-design-for-all/cpu-vs-gpgpu.html
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 04:48, 26 December 2017 (UTC)
thread_title:  External links modified 

message: Does this fall under that category any more?  I mean, is it still possible to buy a new GPU, integrated or otherwise, that doesn't have some level of OpenCL (or CUDA) support?  
Also, in the molecular modelling section: 
† Expected speedups are highly dependent on system configuration. GPU performance compared against multi-core x86 CPU socket. GPU performance benchmarked on GPU supported features and may be a kernel to kernel performance comparison. For details on configuration used, view application website. Speedups as per Nvidia in-house testing or ISV's documentation. 
Is that a direct copy-paste from NVidia's website, or does someone just really like writing disclaimers?  A Shortfall Of Gravitas (talk) 06:17, 27 July 2018 (UTC)
thread_title:  The "emerging technologies" category 

message: Hi, I work at MathWorks on the Parallel Computing team. Thank you for including MathWorks in this page about GPGPU.   There are some updates from 2012, 2017, and 2019 that affect the accuracy of the content.
1. There was a product name change in 2019:  MATLAB Distributed Computing Server is now MATLAB Parallel Server (https://www.mathworks.com/products/matlab-parallel-server.html)
2. MathWorks launched a new product for generating CUDA code in 2017:  GPU Coder (https://www.mathworks.com/products/gpu-coder.html)
3. ArrayFire discontinued sales of Jacket in 2012:  (https://arrayfire.com/blog/tag/jacket/)
We suggest that in the "Implementations" section you change "MATLAB supports GPGPU acceleration using the Parallel Computing Toolbox and MATLAB Distributed Computing Server, and third-party packages like Jacket." to "MATLAB supports GPGPU acceleration using Parallel Computing Toolbox, MATLAB Parallel Server, and GPU Coder."
Thank you for your consideration.  (@MaxDZ8 would you be able to help?) OwlCarbonant54 (talk) 21:00, 24 January 2023 (UTC)
thread_title:  Updates for MATLAB