RERedis · Ops
Community homeHot discussions Latest posts Best of Knowledge base Resources About

Redis · Ops · Newbie question: how should a redis-ops config file be organised?

22
REr/redis-ops·posted by slow_query·2 hours agoInternals

Newbie question: how should a redis-ops config file be organised?

It took me two weeks of on-and-off digging and plenty of wrong turns. Writing the process down as it happened so the next person spends less time.

Worth noting: the official docs do cover this, just in a very inconspicuous spot. I only found it reading the source comments, where the author explains the reasoning — roughly "so that it degrades into predictable behaviour in extreme cases".

Performance44%
Maintainability28%
Ecosystem and community17%
Hiring difficulty11%

37 votes total

10 comments

10 comments

M
Rran_bo·12 minutes ago

Saved. I am reworking this area this week — this saves a lot of wrong turns.

322
Zzhu_zongOP·28 minutes ago

Has anyone run a controlled experiment? I did, reducing it to a single variable, and the difference was 4% — within noise. So I suspect the main cause is something else.

21
Zzhou_yi·12 minutes ago

There is actually a simpler fix that needs no architecture change: move this check up to the gateway and the problem disappears. The cost is one extra lookup at the gateway.

178
Sslow_query·3 minutes ago

A question: what changes in a container with a 512Mi memory limit? That is how we run it in production.

313
Sswoole_lee·2 days ago

One counter-example: below redis-ops 7.4 the semantics of that code are different, so do not copy it verbatim. We got burned in staging and rolled back once.

147
Hhuang_keMod·28 minutes ago

Can you give a minimal reproduction? I ran it locally for ten minutes and could not reproduce on macOS with the latest version.

92
Rrase·3 minutes ago

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

55
Zzhou_yi·28 minutes ago

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

36
Hhuang_keMod·12 minutes ago

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

1
Aalice_dev·12 minutes ago

I just read the redis-ops source — the author actually explains the reasoning in a comment, roughly "so that it degrades into predictable behaviour in extreme cases".

1

This is the post detail page /en/c/redis-ops/post/p9. Posts and comments are generated deterministically from a seeded PRNG, so the same post always renders the same content and the link can be shared, reloaded and indexed. In production this page reads MySQL for the post, Redis for hot-post caching, and fetches the whole comment tree in a single query on the path column.

See the database schema →