Stockfish VS Sidekiq

The Stockfish program can be set to play at strength level 0-20. Estimates of the levels' Elo is provided here: https://github.com/official-stockfish/Stockfish/commit/a08b8...

- and handicapped Stockfish (https://stockfishchess.org).

The whole thing is at https://github.com/magv/bchess, and can be installed with just 'pip install bchess'.

This was the result searching for all the 35 stockfish benchmark positions to depth 6.

Stockfish doesn't have a classical evaluation anymore. And before this, most of the time (around 90%), NNUE was used to evaluate.

If you use ChessBase on a MacBook through Parallels, there's an issue where people have posted Apple Silicon compiles for Windows: https://github.com/official-stockfish/Stockfish/issues/4241

Progress can be found here https://github.com/official-stockfish/Stockfish/wiki/Regression-Tests At 1 thread it has gained +18.3 elo on a balanced book, and +47.03 on UHO (unbalanced) book as well as +39.4 elo for FRC and +65.56 for DFRC. At 8 threads it has gained +14.33 elo on a balanced book and +49.46 on UHO (unbalanced book). Also testing was done on 8 threads with 180+1.8 (this is considered very long time control for fishtest standards) and progress was +9.45 on balanced book and +49.65 on UHO.

Downloads are available temporarily here https://github.com/official-stockfish/Stockfish/releases/tag/stockfish-dev-20230622-a49b3ba7

The strongest version of Stockfish is the latest development version of Stockfish

I am trying to implement Stockfish (a popular chess engine) into my React Native app.

I'd say Sidekiq is the top competitor here.

There's something wrong at Redislabs, it took them over a year to get RESP3 rolled out into their hosted service, you'd expect a rollout of that to be a bit quicker when they're the owner of Redis.

It affected us when upgrading Sidekiq to version 7, which dropped support for older Redis, and their Envoy proxy setup didn't support HELLO and RESP3: https://github.com/sidekiq/sidekiq/issues/5594

That depends on how the `maxmemory-policy` is configured, and queue systems based on Redis will tell you not to allow eviction. https://github.com/sidekiq/sidekiq/wiki/Using-Redis#memory (it even logs a warnings if it detects your Redis is misconfigured IIRC).

Sidekiq https://sidekiq.org/: This one started as an open source project, once it got enough traction, the developer made a premium version of it, and makes money by selling licenses to businesses.

Sidekiq will drop in-progress jobs when a worker crashes. Sidekiq Pro can recover those jobs but with a large delay. Sidekiq is excellent overall but it’s not suitable for processing critical jobs with a low latency guarantee.

https://github.com/sidekiq/sidekiq/wiki/Reliability

> I'm not sure feature withholding has traditionally worked out well in the developer space.

I think it's worked out well for Sidekiq (https://sidekiq.org). I really like their model of layering valuable features between the OSS / Pro / Enterprise licenses.

I was studying Sidekiq's page on rate limiters. The first type of rate limiting mentioned is the concurrent limiter: only n tasks are allowed to run at any point in time. Note that this is independent of time units (e.g. per second), or how long they take to run. The only limitation is the number of concurrent tasks/requests.

The code above isn't idempotent. If you run it twice, it will create two copies, which is probably not what you intended. Why is this important? Because most backend job processors like Sidekiq don't make any guarantees that your jobs will run exactly once.