Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gpu.js – GPU Accelerated JavaScript

gpu.rocks

Post reply on HN
Print view View original

71–80 of 84 posts

Re: Gpu.js – GPU Accelerated JavaScript

#71

Post by sbergot »

davnicwil wrote: post #51
andreasklinger wrote: post #18

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?

I would guess that some people imagine a business model for websites where the user pays with computational power. Using GPU would be a way to make this worthwhile.

Re: Gpu.js – GPU Accelerated JavaScript

#72

Post by kang »

davnicwil wrote: post #51
andreasklinger wrote: post #18

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?

Its the use of hashcash as money, instead of making users see ads.

https://en.wikipedia.org/wiki/Hashcash

Re: Gpu.js – GPU Accelerated JavaScript

#73

Post by thinkfurther »

jingwen wrote: 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.

I love this, but the occasional stutter makes my GC detector tingle :)

Re: Gpu.js – GPU Accelerated JavaScript

#74

Post by urethrafranklin »

haimez wrote: post #36
daxfohl wrote: post #27

Earlier quoted context omitted.

Okay, Bill Gates alone is worth more than twice all the bitcoin ever mined. Apple is worth almost 20x that. So, per risk/reward, probably not a great strategy for either company. https://howmuch.net/articles/worlds-money-in-perspective .

Please adjust your equations for time.

LOL, buttcoin is deflationary.

Re: Gpu.js – GPU Accelerated JavaScript

#75

Post by bastawhiz »

andreasklinger wrote: post #18

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

This will never become a thing. If my phone heats up and dies after twenty minutes because the news site I'm reading is crunching numbers on my phone's GPU, I am (and most other folks on HN are) going to be VERY salty. Compute time on user machines isn't free, and users will notice.

On top of that, display advertising pays when the user sees the ad. Coin mining only pays when the user has completed enough useful work to send results back to the server. The odds of that happening for a huge number of websites are very low.

Re: Gpu.js – GPU Accelerated JavaScript

#79

Post by someguydave »

adventured wrote: post #44
haimez wrote: post #36

Earlier quoted context omitted.

Please adjust your equations for time.

Adjusting to the Gates or Apple timeline doesn't get you anywhere. Bitcoin won't exist in 30 years.

Why not? It has defied such predictions for several years now.

Re: Gpu.js – GPU Accelerated JavaScript

#80

Post by ChoGGi »

codefined wrote: post #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)

I'm also getting the same (sort of) results:

CPU: 0.363s ±6.7%

GPU: 1.077s ±1.8%

Chromium 61, Windows 7, i7-5930k, Nvidia 1080. I did notice my GPU clock didn't move from the idle state.

Post reply on HN