REReplication · Interviews
Community homeHot discussions Latest posts Best of Knowledge base Resources About

Replication · Interviews · After reading the replication-interview core source I finally understand the trade-offs

67
REr/replication-interview·posted by chen_dev·6 hours agoOpen source

After reading the replication-interview core source I finally understand the trade-offs

Some background first. Our setup is replication-interview plus three downstream services, seven figures of daily requests, peaking around nine in the evening.

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".

Documentation first44%
Source code first28%
Just ask someone17%
Run a demo and learn by error11%

114 votes total

17 comments

17 comments

M
Zzhu_zong·12 minutes ago

This is not a replication-interview problem, it is a usage problem. The docs say this API is not thread-safe and you must lock around it yourself.

416
Kkernel_panicMod·28 minutes ago

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

288
Hhuang_ke·just now

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

49
Hhuang_ke·5 hours ago

Worth learning from this debugging approach. We went straight at the logs and took a much longer route.

60
Cchen_dev·2 hours agoedited

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

7
Rrase·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.

18
Cchen_dev·28 minutes agoedited

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.

257
Sslow_query·2 days ago

Sharing our numbers, 8 cores 16GB, same scenario:

| Concurrency | P50 | P99 |
|---|---|---|
| 200 | 12ms | 88ms |
| 500 | 31ms | 340ms |

P99 clearly collapses at 500 concurrency, which lines up with your knee point.

419
Ttang_hao·1 hour ago

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

84
KkiteOP·just now

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

45
Aalice_dev·1 hour agoedited

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.

41
Kkernel_panic·2 hours ago

Worth learning from this debugging approach. We went straight at the logs and took a much longer route.

467
Nnikic·2 hours ago

Agreeing with the above. One addition: with this option enabled the GC count in your metrics doubles, so adjust the alert threshold at the same time or it will keep firing.

88
Ttang_hao·28 minutes ago

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

8
Ttang_hao·just now

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

27
Cchen_dev·12 minutes ago

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

3
Rrase·2 days 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.

1

This is the post detail page /en/c/replication-interview/post/p7. 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 →