Skip to content

Conversation

@otargowski
Copy link
Contributor

@otargowski otargowski commented Dec 3, 2025

Related to #585. This PR will close that issue when I add optimizations in the actual recalculations.
Other performance optimisations mentioned in that issue will arrive in another PR.

The number of rankingsd instances can be controlled by the RANKINGSD_CONCURRENCY setting.
A value of 0 also works. Logging is done to separate files.

It seems that the only change in rankingsd code required for this to work was adding recalc_in_progress=None to the query's filter in choose_for_recalculation.

I tested this with 3 rankingsd instances and ~2500 ranking recalculations on a real/proper sio2 instance, and it indeed resulted in a 3x speedup.

TODO: unset recalc_in_progress on error.

The number of rankingsd instances can be controlled by the
RANKINGSD_CONCURRENCY setting.
@otargowski otargowski self-assigned this Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant