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

61–70 of 84 posts

Re: Gpu.js – GPU Accelerated JavaScript

#61

Post by PetahNZ »

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)

To be fair, that is pretty old GPU. GPGPU's have advanced a lot more than CPU's as of recent.

Re: Gpu.js – GPU Accelerated JavaScript

#62

Post by PetahNZ »

sscarduzio wrote: post #55
Retr0spectrum wrote: post #54

Earlier quoted context omitted.

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.

Yea had that happen to me before. Turns out the solder went bad and cracked from to many heat cycles. Returned it and got it replaced.

Re: Gpu.js – GPU Accelerated JavaScript

#64

Post by moron4hire »

jeff_friesen wrote: post #21
jeff_friesen wrote: post #20

Earlier quoted context omitted.

I've been watching this project for over a year. There is quite a bit of work and care put into it. https://github.com/gpujs/gpu.js/graphs/contributors

However, I'm not claiming it's production ready, just that it's more than a weekend project.

"production ready" is a state of mind, not project.

Re: Gpu.js – GPU Accelerated JavaScript

#65

Post by m_mueller »

chongli wrote: post #50
m_mueller wrote: post #40

Earlier quoted context omitted.

the beginning of the end of adblock :(

Ad blocking will always work as long as: a) ad networks insist on having users connect to their servers and b) users have the ability to blacklist said servers.

If you treat it like proof-of-work system it's rather depending on c): Making sure that search engines can still index your content. Because if that is not a requirement it's actually rather trivial to defeat any ad blocker: pose a computational problem that takes x seconds to compute on average hardware. Show ad while computation is going on. Only serve content once client sends back the answer. Sure, blockers can still block the ad itself, but it will just make the user stare at a blank screen.. or more likely loose him forever ;).

Re: Gpu.js – GPU Accelerated JavaScript

#67

Post by Narishma »

PetahNZ wrote: post #62
sscarduzio wrote: post #55

Earlier quoted context omitted.

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

Yea had that happen to me before. Turns out the solder went bad and cracked from to many heat cycles. Returned it and got it replaced.

I don't see how that can happen in this case since the GPU is in the same chip as the CPU.

Re: Gpu.js – GPU Accelerated JavaScript

#69

Post by acomjean »

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)

FWIW I had the gnu at 85% faster with built in gnu (Intel Iris) intel i5.

Re: Gpu.js – GPU Accelerated JavaScript

#70

Post by drngdds »

snarfy wrote: post #19

Things like this make me fear banner ads mining bitcoins (not that they aren't already).

Nitpick: Bitcoins can't effectively be mined on anything but specialized ASIC hardware. Not even high-end GPUs. They could theoretically mine other cryptocurrencies, though.
Post reply on HN