Vue · Advanced · vue-pro under load on an 8-core 16GB box — full benchmark scripts included

7
VUr/vue-pro·posted by tang_hao·3 days agoReview

vue-pro under load on an 8-core 16GB box — full benchmark scripts included

Some background first. Our setup is vue-pro plus three downstream services, seven figures of daily requests, peaking around nine in the evening.

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

The first thing was to collapse the variables. We were changing config and upgrading the version at the same time, and afterwards nobody could say which change caused what. We rolled back to moving one variable at a time, re-ran three times, and only then did the curve settle. Tedious, but not skippable.

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

3 comments

M
Bbob_chen·1 hour ago

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

415
Kkite·just now

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.

382
Rran_bo·just now

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

8

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