MFMonorepo Frontend · Q&A
Community homeHot discussions Latest posts Best of Knowledge base Resources About

Monorepo Frontend · Q&A · Built a visual debugging panel for monorepo-frontend-qa over the weekend

58
MFr/monorepo-frontend-qa·posted by ran_bo·3 days agoExperience

Built a visual debugging panel for monorepo-frontend-qa over the weekend

Most monorepo-frontend-qa articles stop at "how to use it" and never cover "when not to use it". This is an attempt at the second half.

What genuinely surprised me was the tail. The average looked great while P99 jumped by an order of magnitude past some threshold. The cause was not monorepo-frontend-qa itself but our upstream connection reuse — the load test traffic was too clean and hid the long-tail requests.

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

99 votes total

28 comments

28 comments

M
Nnikic·2 days 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.

494
Rran_bo·28 minutes ago

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

345
Mmike_xu·1 hour ago

We have run this in production for two years without hitting it. That said, we never reached this scale, so our experience is not really evidence here.

281
Cchen_dev·12 minutes ago

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

131
LlinlinOP·12 minutes 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.

34
Aalice_dev·2 days 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.

66
Hhuang_ke·just now

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.

277
Rrase·just now

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

236
RraseOP·2 days ago

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

50
Llinlin·2 days agoedited

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

73
Wwinter·2 days ago

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

188
Hhuang_ke·28 minutes agoedited

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.

41
Aalice_dev·2 days ago

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

426
Lli_ming·2 days 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.

318
Hhuang_ke·3 minutes ago

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

140
Mmike_xu·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.

283
Lli_ming·just now

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

35
Cchen_dev·5 hours ago

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

33
Ddev_zhou·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.

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

24
Kkernel_panic·3 minutes ago

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

9
Rran_bo·1 hour 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.

96
Llinlin·2 days agoedited

We have run this in production for two years without hitting it. That said, we never reached this scale, so our experience is not really evidence here.

141
Kkernel_panic·5 hours ago

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

2
Aalice_dev·yesterday

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

13
Mmike_xu·yesterday

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

6
Ttang_hao·2 days 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.

1
Oops_wangMod·3 minutes ago

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

94

This is the post detail page /en/c/monorepo-frontend-qa/post/p2. 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 →