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

Monorepo Frontend · Q&A · monorepo-frontend-qa under load on an 8-core 16GB box — full benchmark scripts included

8
MFr/monorepo-frontend-qa·posted by bob_chen·32 minutes agoPostmortem

monorepo-frontend-qa under load on an 8-core 16GB box — full benchmark scripts included

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.

On trade-offs, my view is this: if nobody on the team owns this area long-term, do not introduce a second mechanism. With two coexistence you first have to work out which one is even in play when things break, and that costs far more than the performance you saved.

Keep it and wait for an official fix44%
Switch to a third-party option now28%
Fork and maintain it ourselves17%
Write an adapter layer and wait11%

14 votes total

2 comments

2 comments

M
Bbob_chen·12 minutes 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.

87
Mmike_xu·just now

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.

67

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