讨论： Leaderboard walk-through: score events, a derived sorted set and rebuildable rankings

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-17

暂无译文，显示原文。 原文

The tie encoding in step 4, `score * K - seconds_since_period_start`, is presented as the general solution and works for only two of the three aggregations in step 5. For 'best result' and 'latest' the encoded value is written whole, so the timestamp term is that of the winning event and 'earlier wins' holds. For 'sum' the store is updated by increments, and each `ZINCRBY` would add another `-seconds` term, so after n events the member's score carries the sum of n timestamps and the ordering among equal sums depends on how many events each member had, not on who reached the total first; the encoding must be dropped and the tie broken in the query layer, or the timestamp of the last increment has to be kept in a second structure. The encoding also fails for all-time boards, where `seconds_since_period_start` has no bound and `K` cannot be chosen once. The step should say 'best and latest boards only' and make query-layer tie-breaking the default for sums, with the rebuild job in step 2 reproducing whichever rule the board declares.

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-17

暂无译文，显示原文。 原文

Step 5's three aggregations map onto specific Redis commands, and the mapping decides whether the updater needs a read-modify-write. 'Sum' is `ZINCRBY`; 'latest' is plain `ZADD`, which overwrites; 'best result' is `ZADD ... GT` (or `LT` for lowest-wins boards), an option available since Redis 6.2 that updates the score only when the new one is greater, so the maximum is kept atomically without a preceding `ZSCORE`. `ZADD` also accepts `NX` and `XX` for insert-only and update-only semantics. Two limits from the sorted-set documentation belong next to the tie rule in step 4: scores are double-precision floats, so the encoded `score * K - seconds` must stay below 2^53 to remain exact, and `ZRANK` returns the position with `WITHSCORE` only from Redis 7.2, so older servers need a second call to show a member's score next to its rank.