Live data from Hacker News

Lichess Analysis Board with Stockfish 8 in Asm.js

lichess.org

1–8 of 8 posts

Re: Lichess Analysis Board with Stockfish 8 in Asm.js

#5
post #3

WebAssembly is supported as well. It has become much faster a few months back when it supported WebAssembly. On my system and using forefox it was 340 knodes/s with asm.js. With WebAssembly it is 600+ knodes/s

Weirdly enough, I was thinking webassembly but I wrote asm.js. I'm very surprised this happened, but apparently it did.

Re: Lichess Analysis Board with Stockfish 8 in Asm.js

#6
post #5
post #3

WebAssembly is supported as well. It has become much faster a few months back when it supported WebAssembly. On my system and using forefox it was 340 knodes/s with asm.js. With WebAssembly it is 600+ knodes/s

Weirdly enough, I was thinking webassembly but I wrote asm.js. I'm very surprised this happened, but apparently it did.

Actually 'WebAssembly' appeared in the title for few minutes, but then it was edited to 'Asm.js'

Re: Lichess Analysis Board with Stockfish 8 in Asm.js

#7
Lichess tries to use (in this order): PNaCl, WASM, asm.js.

PNaCl required almost no modifications to Stockfish (https://github.com/niklasf/stockfish.pexe), supports multithreading and is still the fastest.

WASM and asm.js require the same patches (https://github.com/niklasf/stockfish.js). Most notably WASM does not yet have multi-threading. In the original Stockfish one dedicated thread is listening for new commands. Instead now the main search thread (since it's the only thread) has to check for new commands from time to time, which costs a bit of performance.

Re: Lichess Analysis Board with Stockfish 8 in Asm.js

#8
post #6
post #5

Earlier quoted context omitted.

Weirdly enough, I was thinking webassembly but I wrote asm.js. I'm very surprised this happened, but apparently it did.

Actually 'WebAssembly' appeared in the title for few minutes, but then it was edited to 'Asm.js'

I was suspecting so. I presume whoever did it followed the link, noticed the engine was using asm.js and not wasm, and thought I was mistaken. But truly what the engine uses depends on the browser and its configuration.