7 ms·
Stockfish.js
- tromp 5y agoChess engine performance is dependent on fast 64-bit integer operations. How does this implementation deal with javascript ints being limited to 32-bits? Is emscriptem somehow able to generate code using WASM's 64 bit ints?
- threatofrain 5y agoI believe JS has access to 64-bit.
- petilon 5y agoJS has access to 64-bit floating point, not int.
- tyleregeto 5y agoJS has BigInt support, a quick Google tells me this is supported by wasm. I'm not sure if they are doing that here or not. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
- tempay 5y agoBigInt is often orders of magnitude less performant than int32 so it's unlikely to be helpful in this situation.
- pwython 5y agoUnless you're compiling from something like Cheerp.
- Kubuxu 5y agoIt uses WASM which has 64bit integers.
- brrrrrm 5y ago^ this. Ref: https://webassembly.github.io/spec/core/syntax/types.html#syntax-numtype https://webassembly.github.io/spec/core/syntax/types.html#sy...
- johndough 5y agoSeems to be true. https://mbebenita.github.io/WasmExplorer/ https://mbebenita.github.io/WasmExplorer/ emits i64.mul which is compiled to imul rax, rdi by firefox for the following code snippet: #include <stdint.h> uint64_t multiply(uint64_t a, uint64_t b){ return a * b; }
- Cthulhu_ 5y agoProbably using JS's BigInt https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
- tiffanyh 5y agoHow does this compare to stockfish-nnue.wasm [0] which is used on Lichess.org [1] [0] https://github.com/hi-ogawa/Stockfish https://github.com/hi-ogawa/Stockfish [1] https://lichess.org/source https://lichess.org/source
- jokethrowaway 5y agoNNUE is heavier but considered better
- perihelions 5y agoThat's not the distinction here: these are two different Stockfish JS projects, both of which port the NNUE version.
- perihelions 5y agoA related fork [0] powers the web-based tool on Lichess [1]. It's a notable example of WASM in widespread use (I believe it's WASM-by-default on every browser now). [0] https://github.com/hi-ogawa/Stockfish https://github.com/hi-ogawa/Stockfish [1] https://lichess.org/analysis https://lichess.org/analysis (in the top-right corner: "Stockfish 14+ NNUE in local browser") (edit: fixed link to the correct fork)
- tiffanyh 5y agoFYI - the version you linked to is the “Slower fallback versions of Stockfish for browsers (C++, WebAssembly, JavaScript)” according to Lichess. https://lichess.org/source https://lichess.org/source EDIT: nevermind, looks like you changed the link.
- perihelions 5y agoThanks, corrected link!
- WithinReason 5y agoI wonder why Lichess doesn't use multithreading, it was working in a previous version. I mean Brave can use 2 threads but I've seen 8/16 max threads before.
- tiffanyh 5y agoLichess doesn’t? There’s reference to thread support in the library documentation. https://github.com/hi-ogawa/Stockfish#threads https://github.com/hi-ogawa/Stockfish#threads
- deleted 5y ago[deleted]
- JacobLinney 5y agoLichess on chrome let's me use however many logical processors I have. For whatever reason I can only get a single thread on Firefox. I'm not sure why either, because a while back I could use how ever many threads I wanted on Firefox.
- tediousdemise 5y agoOpened a random cpp source file, saw goto statements, and noped out of there real quick.
- Cpoll 5y agohttps://github.com/nmrugg/stockfish.js/search?q=goto https://github.com/nmrugg/stockfish.js/search?q=goto Five occurrences of goto, for anyone that's curious. The code is pretty easy to read, good variable names, some explanatory comments. The gotos don't make spaghetti. I'm inclined to think the writers knew what they were doing, though goto offends my sensibilities as much as anyone. Could anyone with more experience explain the pattern? Why gotos for control flow along with >thousand line functions?
- mhink 5y agoInteresting. I was looking at the algorithm in evaluate.cpp [0] and it seems to be the case that the control flow is pretty much just an alternative to if-statements... which, personally, I find to be more readable than it'd otherwise be if it were heavily nested. I'm open to arguments otherwise, though. Consider two alternatives (written in pseudo-Javascript, I guess): let xyz = 0; if (!condition1) { doSomething(); xyz = getValueSomehow(); if (!condition2) { doSomethingElse(); xyz += getSomeOtherValueSomehow(); } } finishUpBusinessLogic(); return xyz; that seems much less readable than: let xyz = 0; if (condition1) goto done; doSomething(); xyz = getValueSomehow(); if (condition2) goto done; doSomethingElse(); xyz += getSomeOtherValueSomehow(); done: finishUpBusinessLogic(); return xyz; 0: https://github.com/nmrugg/stockfish.js/blob/d96c98872103c60b713e986901dd1e22986e9280/src/evaluate.cpp https://github.com/nmrugg/stockfish.js/blob/d96c98872103c60b...
- kilburn 5y agoThe hidden side-effects of your example code make it hard to reformat, but in general people don't advocate for your first example. The push is more towards defining smaller logic blocks (with names that hint at what they do): def computeSomething() { if (condition1) return 0; let value = getValueSomehow(); if (condition2) return value; doSomethingElse(); return value + getSomeOtherValue(); } let value = computeSomething(); finishUpBusinessLogic(); return value;