Tableau · Code review · Building an internal platform with tableau-review from scratch: architecture and decision log

2
TAr/tableau-review·posted by zhu_zong·6 hours agoTooling

Building an internal platform with tableau-review from scratch: architecture and decision log

Short version: tableau-review 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.

What genuinely surprised me was the tail. The average looked great while P99 jumped by an order of magnitude past some threshold. The cause was not tableau-review itself but our upstream connection reuse — the load test traffic was too clean and hid the long-tail requests.

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%

3 votes total

2 comments

2 comments

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

354
Ttang_haoMod·12 minutes ago

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

26

This is the post detail page /en/c/tableau-review/post/p12. 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 →