Turbo.js – GPGPU made simple • Hacker News Board

Re: Turbo.js – GPGPU made simple

#21

Post by franciscop » Sat, Nov 05, 2016, 8:54 AM UTC

minxomat wrote: post #19

andreapaiola wrote: post #18

Ah snap! There was no error compiling the test kernel or running it, but the numbers don't check out. Please report your browser (+ version) and hardware configuration to us, so we can try to fix this. Deviation was 0.3373333334457129. console: Values are: 0.00900000031106174 and 1.0210000006482005 --------------------- Chrome on Ubuntu on Intel NUC

Please report to http://github.com/turbo/js . I can't track issues on HN.

Well you are here, what I did in the past when some of my projects got into HN is just copy/paste those reports in the issue tracker in Github. A bit of work but I got great reports in HN that didn't want to waste.

Re: Turbo.js – GPGPU made simple

#22

Post by homero » Sat, Nov 05, 2016, 9:32 AM UTC

bradknowles wrote: post #3

Does it really do anything on mobile? Anyone got some example results they can share with us, including hardware/OS/software you're running and what kind of speed up was found?

Works great on note 4 and v20

Re: Turbo.js – GPGPU made simple

#23

Post by minxomat » Sat, Nov 05, 2016, 9:36 AM UTC

homero wrote: post #22

bradknowles wrote: post #3

Does it really do anything on mobile? Anyone got some example results they can share with us, including hardware/OS/software you're running and what kind of speed up was found?

Works great on note 4 and v20

Nice!

Re: Turbo.js – GPGPU made simple

#24

Post by erpellan » Sat, Nov 05, 2016, 11:01 AM UTC

frameBufferStatus was false. frameBufferStatus.message is undefined.

if (!frameBufferStatus) throw new Error('ERROR: (fatal): ' + frameBufferStatus.message);

Chrome on Windows 10 + AMD R9/280.

Re: Turbo.js – GPGPU made simple

#25

Post by ooqr » Sat, Nov 05, 2016, 11:57 AM UTC

As for many others, this does not work for me, yet I'm eager to try this.

Re: Turbo.js – GPGPU made simple

#26

Post by Cyph0n » Sat, Nov 05, 2016, 1:07 PM UTC

minxomat wrote: post #17

michwill wrote: post #16

Earlier quoted context omitted.

Same for me. Linux/Chromium or Linux/Firefox

Hi, please report any issues to the repo at http://github.com/turbo/js . The more hardware combo test data I have, the sooner I can debug these faults. If you have any friends with exceptionally weird configs, please get them to test, too :-) BTW: If you get the "Ah snap" error, there is some diagnostic data in the console. Please include that in any issue report. Cheers.

Small note: I'd recommend naming the repo `turbo` or `turbojs`, instead of just `js`.

Re: Turbo.js – GPGPU made simple

#27

Post by pmontra » Sat, Nov 05, 2016, 1:12 PM UTC

bradknowles wrote: post #3

Does it really do anything on mobile? Anyone got some example results they can share with us, including hardware/OS/software you're running and what kind of speed up was found?

On Android it works in Opera and it doesn't in Firefox.

Re: Turbo.js – GPGPU made simple

#28

Post by msimpson » Sat, Nov 05, 2016, 2:25 PM UTC

Great work minxomat, and under 200 LOC as well.

Re: Turbo.js – GPGPU made simple

#29

Post by ris » Sat, Nov 05, 2016, 3:31 PM UTC

I thought something exciting had been done here but it's been a long time since "GPGPU" meant "kernels written in GLSL".

Re: Turbo.js – GPGPU made simple

#30

Post by deadcast » Sat, Nov 05, 2016, 4:38 PM UTC

blurbleblurble wrote: post #15

Seems cool... but it doesn't work for me! > Ah snap! There was no error compiling the test kernel or running it, but the numbers don't check out. Please report your browser (+ version) and hardware configuration to us, so we can try to fix this. Deviation was 0.33731377391086426. I'm on linux 4.7 + chromium 53 with Intel 4000 graphics

Yeah I got that error as well. I'm using IceCat 38.8.0 on Trisquel 7.0 with a geforce 8400gs.