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

Monorepo Frontend · Q&A · Hiring: remote monorepo-frontend-qa engineer (full-time, long-term)

18
MFr/monorepo-frontend-qa·posted by dev_zhou·3 hours agoHelp

Hiring: remote monorepo-frontend-qa engineer (full-time, long-term)

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.

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.

Image placeholder · object storage in production
POST /api/uploads → CDN origin pull
12 comments

12 comments

M
Kkite·2 hours ago

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

495
Ttang_hao·3 minutes ago

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

481
Kkernel_panic·12 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".

418
Zzhu_zongMod·28 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.

52
Kkernel_panic·12 minutes 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.

430
Zzhou_yi·3 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.

47
Sslow_query·just now

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

10
Nnikic·12 minutes agoedited

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

373
Zzhou_yi·just now

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

1
Kkite·just now

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.

125
Lli_ming·just nowedited

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

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