-
Notifications
You must be signed in to change notification settings - Fork 260
Linux & OS X Deviation Errors #1
Comments
Thanks for reporting. I'll look into that. Also, I'd be interesting in test results from stable Chrome on your hardware. |
Keep up the good work! Yes, the test works fine on Chrome on the same machine: Test results: |
I originally designed this as a chrome experiment. There are some issues with other WebGL pipelines in other browsers (Chrome being the fastest, followed by FireFox, then Edge), that are intermittent and almost impossible to debug. Thanks for the test data, that gives me a broader idea of the problems (sharing helps with data collection ;-)) |
I also received this error, deviation for me was |
I'm getting this same issue on linux kernel 4.7.6, running Chromium 53.0.2785.143 with Intel i5-3320M CPU + HD Graphics 4000 GPU |
@micahscopes Can you also provide the console output? There should be diagnostic data there, |
@turbo sure:
|
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. Chrome on Ubuntu 14.04 64 bit on Intel NUC i3-4010U from #2 |
Deviation was 0.020666667027398944. Values are: on Firefox Developer Edition 51.0a2 (2016-10-17) (64-bit) from #2 |
I also got an error:
The meter shows a 0.98 improvement On the console:
My Software/Hardware: Firefox 49.0.2 Another note: I've successfully used web workers to x4 the performance, but that's just for the CPU and not the GPU. A fallback would be nice though (: From #3, CC @franciscop |
In the https://turbo.github.io website, under the JAVASCRIPT & TURBO.JS section, I got an "Ah snap!" error message with deviation of In my JavaScript console, I got the following message:
Browser: Google Chrome Version 54.0.2840.87 (64-bit) From #6. CC @kritixilithos |
Another oh snap, deviation: 8290839237929643
Ubuntu 16.04, Chromium 53.0.2785.143, CPU is "AMD E-450 APU with Radeon(tm) HD Graphics", GPU is Radeon HD 6320 "Chipset: "AMD Radeon HD 6300 Series Graphics" (ChipID = 0x9806)". (EDIT: similar result with Firefox 49.0.2.) |
Wildly varying errors (Ubuntu 16.10, Vivaldi 1.5.655.3 (Official Build) dev (64-bit) (uses Chromium 54.0.2840.89)) - worked fine the first time. Experimental WebAssembly, Experimental Validate Asm.js and convert to WebAssembly when valid, experimental canvas features, 2D canvas dynamic rendering mode switching, Extensions on chrome:// URLs, Save Page as MHTML, Experimental JavaScript and GPU rasterisation enabled, GPU rasterisation MSAA sample count is 0 (in case any of this is somehow useful). Celeron N2840 @ 2.16GHz x 2 processor, Bay Trail graphics Note: Worked fine the first time, which is before I updated Vivaldi and with all flags off.
|
Ubuntu 14.04 - CPU AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ - GPU Gallium 0.4 on AMD RV635
For Chrome Version 54.0.2840.90 (64-bit)
http://webglreport.com/ for FF says WebGL 1 supported, WebGL2 not supported
|
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 137920146396501.34. Chromium Version 53.0.2785.143 Built on Ubuntu , running on LinuxMint 18 (64-bit) Let me know if you need anything else! from #9 |
MacBook Air (13-inch, Mid 2013) On Safari 10.0.1. Deviation was 0.007000000138456623. |
I got one too:
I'm on the following:
I'm using the AMD APU as my graphics chip. I can't think of any other pertinent information that I could provide. I'm on Manjaro so everything in my graphics stack should be relatively up to date. Edit: I don't know if this is helpful but I've just done a test with my laptop and got a deviation of similar magnitude despite it the only difference between these two systems being their hardware. They are both running Manjaro (my desktop and laptop). My laptop is a Thinkpad x220 so I'm not sure if that helps narrow down where the issue is coming from. |
|
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.003999999957159162. Safari Version 10.0 (11602.1.50.0.10) |
All browsers give the same errors. |
Numbers varied wildly |
I noticed something interesting on my desktop. If I keep calling
If I initialize those floats, the errors stop under the same circumstances:
I think you may be getting garbage.
Desktop Specs Update
It appears the deviation is still random. |
@msimpson, |
P.s., when this stabilizes you will probably find me using it to draw fractals. |
Variables are initialized now. I always forget this, I'm just used to the much more relaxed AMD GLSL flavor. Please test again and see if it does anything for you 🎱 . |
@msimpson That deviation is pretty good actually. If it doesn't massively exceed this, I might dare to call it usable. |
Well. That fixes it for me:
Please just leave "fixed" if that resolved the issue for you. |
"fixed" looks like I'm getting ~5x speedups on the front page 👍 👍 👍 👍 |
fixed |
works for me, I get 4.15 |
I modified
So that's an accuracy of 99.78% to within plus or minus one thousandth of each other, where no individual iteration drifted further than plus or minus three tenths overall. Not too bad, considering the type conversions and variance of IEEE 754 at play. |
That's seems to be pretty much exact. I actually expect to be the GPU results to be more precise. Thanks for the test. |
@turbo |
fixed in FF and Chrome. |
I also had a low deviation on Safari |
In Safari
From #17. |
Safari 10.0.1 (12602.2.14.0.7), macOS Sierra
Chrome 54.0.2840.98 (64-bit) and Firefox 49.0.2 are both working, Firefox getting the best score. |
It works for me now. |
A mysterious warning appears in the console:
Relevant line turbo.js:184:
Config
|
Safari Version 10.0.1 (12602.2.14.0.7)
MacOS Sierra 10.12.1
MacBook Pro late 2012
Intel HD Graphics 4000 1536 MB
The text was updated successfully, but these errors were encountered: