Just some feedback that Im very happy we can use PNACL again. I'm happy to move on to something new as long as the performance doesnt go down the drain ..
Was getting only a fraction of the performance with only 8 logical cpu's being used. As well as the engine not loading frequently.
So do I have a wrong setting in my browser (chrome) or did Lichess just go back to WASM bringing all analysis back down to 1 core?
If your Chrome is still stuck on WASM, maybe try toggling the web assembly settings in Chrome (chrome://flags/#enable-webassembly-threads) and/or clear cookies/cache.
Thanks .. I've now uninstalled/reinstalled chrome, cleared cache/settings and messed around with the settings until I was blue in the face :-)
My findings are that once the engine starts up as WASM it won't revert to WASMX or PNACL until I cleared cache/settings again.
Then it will startup as WASMX, after enabling all 5 flags to do with (nacl) it will (again after many attempts) start up with PNACL (also on new tabs) until the browser is closed then back to WASM (no PNACL again) ..
I've reproduced this whole cycle a few times now..
Could it be that the last fix/release was not deployed to every server instance and I'm 'randomly' connecting to Lichess websites with different code ?
Thanks,
Berry
Ok, it seems that PNACL has been removed? Are we stuck with WASM now?
Nevermind, I had to clear my cache/settings... weird.
This topic has been archived and can no longer be replied to.