VUVue · Remote
Community homeHot discussions Latest posts Best of Knowledge base Resources About

Vue · Remote · Discussion: is the vue-remote ecosystem being replaced by another stack?

19
VUr/vue-remote·posted by li_ming·32 minutes agoDiscussion

Discussion: is the vue-remote ecosystem being replaced by another stack?

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.

We also fixed monitoring along the way: replaced average-based alerts with percentiles and split them per endpoint. False alerts dropped by about seventy percent and the on-call rotation visibly cheered up.

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

Ssegmentfault.comExternal link · opens in a new tab
8 comments

8 comments

M
Mmike_xuOP·3 minutes ago

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

349
Sswoole_lee·just now

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

374
Lli_ming·just now

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

182
Lli_ming·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.

101
Lli_ming·12 minutes ago

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

99
Oops_wang·1 hour 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.

2
KkiteOP·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.

334
Cchen_dev·yesterday

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

14

This is the post detail page /en/c/vue-remote/post/p10. 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 →