Jupyter · Advanced · Ten jupyter-pro anti-patterns — how many are you guilty of?

3
JUr/jupyter-pro·posted by dev_zhou·just nowReview

Ten jupyter-pro anti-patterns — how many are you guilty of?

Short version: jupyter-pro 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.

One last trap: in container environments remember to adjust the memory-related parameters in step. Otherwise the host limit and the process expectation disagree, and the symptom is intermittent, unreproducible failure.

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

1 comments

M
Lli_ming·just now

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

250

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