Live data from Hacker News

Gpu.js – GPU Accelerated JavaScript

gpu.rocks

51–60 of 84 posts

Re: Gpu.js – GPU Accelerated JavaScript

#51

Is js via gpu (WebGL i assume) already efficient enough to make the concept of "computation time instead of banners" finally viable?

I've never come across this concept before. What is it? Is it something like, to see the page content, you must have a key which is either time-consuming to compute, or is just given to you if you first view an ad?

Re: Gpu.js – GPU Accelerated JavaScript

#53
post #42

I've built an animated raytracer using this library. http://raytracer.crypt.sg The compile-able JavaScript subset is still fairly limited, so vector operations are quite painful. Beyond that, it's a great library to start with for parallel computation in the browser if you have no background in WebGL/GLSL.

It reminds me the path-traced online game, that I made three years ago :) http://powerstones.ivank.net/

Re: Gpu.js – GPU Accelerated JavaScript

#55

After running these GPU benchmarks I had to reboot my Macbook because all my open windows went scrambled and unreadable. Not sure what's the root cause for this.

Sounds like your GPU is dying.

Are you serious? It's just 1 year old.. Intel Iris Graphics 6100 1536 MB in my MBP 13, Early 2015.

Re: Gpu.js – GPU Accelerated JavaScript

#56
post #42

I've built an animated raytracer using this library. http://raytracer.crypt.sg The compile-able JavaScript subset is still fairly limited, so vector operations are quite painful. Beyond that, it's a great library to start with for parallel computation in the browser if you have no background in WebGL/GLSL.

It reminds me the path-traced online game, that I made three years ago :) http://powerstones.ivank.net/

Nice but please, at least, put an audio off button :)

Re: Gpu.js – GPU Accelerated JavaScript

#57

After running these GPU benchmarks I had to reboot my Macbook because all my open windows went scrambled and unreadable. Not sure what's the root cause for this.

Is it repeatable? It could be a driver problem. If it doesn't happen again, it may be path dependent on other things you've run since boot. Or it could be bad hardware, or bad cooling.

It's definitely not the fault of the GPU benchmarks - that shouldn't cause system wide problems.

Re: Gpu.js – GPU Accelerated JavaScript

#59
post #14

How does this compare to Turbo.js?

turbo.js is a barebones library (a port of NanoCL[1]). It

- doesn't support hardware or drivers that still don't support hp float textures (all things Apple basically)[2]

- requires you to use GLSL

(I'm the creator of turbo.js)

[1] - https://github.com/turbo/NanoCL [2] - https://github.com/turbo/js/blob/dev/turbo.js#L45-L135

Re: Gpu.js – GPU Accelerated JavaScript

#60
Is anyone else getting consistently slower speeds on their GPU compared with their CPU? I seem to be getting:

CPU: 0.426s ±7.6%

GPU: 2.399s ±4.7%

Running Chrome, Latest Stable. Windows 7. It seems odd to me that it would take 6x longer when my graphics card (GTX 690) would theoretically be much faster than my CPU (Intel i7-3930k)

Post reply on HN