With a modern browser, the trend is to load more and more computing on the front end. For graphic purpose GPU can now wisely be used and is becoming required more and more. The road opened with WebGL is obviously followed by General Purpose GPU technologies: WebCL (Khronos group) or River Trail (Intel). But WebGL is quite young and unfortunately we are not very close to see a full implementation of those parallel computing technic coming soon this year.
Take care of Buffers that aren’t initialized in a 2D square texture, because it will have noise padded to complete the squared space. You may also prefer reading the source code itself more than the documentation, which doesn’t fully explain all the features and functions.
If using OpenGL as a workaround to CUDA or OpenCL has always been part of the GPGPU computing culture, its technique doesn’t appear to have spread to web technologies. Hopefully WebGL2.0 based on OpenGLes3.0 will see more of these solutions. Examples and demos can be seen in Three.js or other GPGPU WebGl hack (See links below). It would be interesting to see some “classic” GPU hack implemented in WebGL such as the Pingpong FBO which allows a simultaneous read/write operation on the buffer.
Here is a table of tested numbers under WebGLCL: the 3rd row is a result on your own GPU and on a compatible GPU.
|CPU||Tested GPU*||Your GPU|
|0||-2.3650443381484365e-8||Your browser doesn’t support WebGL|