Vue · Remote · Postmortem: how we exhausted the connection pool in vue-remote

5
VUr/vue-remote·posted by bob_chen·2 days agoOpen source

Postmortem: how we exhausted the connection pool in vue-remote

Short version: vue-remote needs almost no tuning at small and medium scale — the point where it starts to hurt is much further out than most people assume. Full measurements below.

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

Documentation first44%
Source code first28%
Just ask someone17%
Run a demo and learn by error11%

9 votes total

1 comments

1 comments

M
Rran_bo·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.

202

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