Burp Suite · Job board · Why this burpsuite-jobs pattern gets slow in production: a source-level explanation

3
BSr/burpsuite-jobs·posted by nikic·2 days agoExperience

Why this burpsuite-jobs pattern gets slow in production: a source-level explanation

Short version: burpsuite-jobs 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.

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.

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

2 comments

M
Kkernel_panic·28 minutes ago

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

27
Sslow_query·3 minutes ago

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

3

This is the post detail page /en/c/burpsuite-jobs/post/p4. 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 →