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

Replication · Interviews · Choosing replication-interview: I turned 5 options into a side-by-side comparison

23
REr/replication-interview·posted by bob_chen·1 hour agoReview

Choosing replication-interview: I turned 5 options into a side-by-side comparison

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

One last trap: in container environments remember to adjust the memory-related parameters in step. Otherwise the host limit and the process expectation disagree, and the symptom is intermittent, unreproducible failure.

Self-host — full control44%
Managed service — less work28%
Hybrid: core self-hosted17%
Not decided yet11%

39 votes total

11 comments

11 comments

M
Sslow_queryOP·12 minutes agoedited

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.

265
Cchen_dev·2 hours ago

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.

382
Bbob_chenOP·2 days 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".

9
NnikicMod·1 hour agoedited

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

339
Bbob_chen·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.

266
Bbob_chen·3 minutes agoedited

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

233
Hhuang_ke·yesterday

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.

86
NnikicOP·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.

4
Aalice_dev·3 minutes ago

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

7
Aalice_dev·28 minutes ago

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

1
Wwinter·12 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.

102

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