CTCLI Tools · Career
Community homeHot discussions Latest posts Best of Knowledge base Resources About

CLI Tools · Career · Two weeks with cli-tools-career: what feels right and what drives me up the wall

27
CTr/cli-tools-career·posted by mike_xu·yesterdayHelp

Two weeks with cli-tools-career: what feels right and what drives me up the wall

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.

On trade-offs, my view is this: if nobody on the team owns this area long-term, do not introduce a second mechanism. With two coexistence you first have to work out which one is even in play when things break, and that costs far more than the performance you saved.

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

46 votes total

11 comments

11 comments

M
Rran_boOP·just now

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

465
Rran_bo·28 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.

502
Aalice_devOP·just nowedited

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

244
Kkite·2 days 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.

143
Bbob_chen·28 minutes ago

Saved. I am reworking this area this week — this saves a lot of wrong turns.

81
Hhuang_keOP·28 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.

17
Zzhou_yi·3 minutes 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.

26
Zzhou_yi·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.

1
Rran_bo·28 minutes ago

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

14
Nnikic·12 minutes ago

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

38
Zzhou_yiMod·1 hour ago

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

10

This is the post detail page /en/c/cli-tools-career/post/p7. 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 →