TMtmux · Advanced
Community homeHot discussions Latest posts Best of Knowledge base Resources About

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

12
TMr/tmux-pro·posted by zhu_zong·2 days agoTooling

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

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.

Image placeholder · object storage in production
POST /api/uploads → CDN origin pull
6 comments

6 comments

M
NnikicOP·3 minutes 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.

161
Mmike_xu·2 hours ago

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.

297
Rran_bo·12 minutes agoedited

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

110
Llinlin·12 minutes ago

Agreeing with the above. One addition: with this option enabled the GC count in your metrics doubles, so adjust the alert threshold at the same time or it will keep firing.

61
Kkite·3 minutes ago

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

53
Llinlin·3 minutes agoedited

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

36

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