ECEdge Computing · Resources
Community homeHot discussions Latest posts Best of Knowledge base Resources About

Edge Computing · Resources · Postmortem: how we exhausted the connection pool in edge-computing-resources

3
ECr/edge-computing-resources·posted by linlin·3 days agoDiscussion

Postmortem: how we exhausted the connection pool in edge-computing-resources

Most edge-computing-resources articles stop at "how to use it" and never cover "when not to use it". This is an attempt at the second half.

The first thing was to collapse the variables. We were changing config and upgrading the version at the same time, and afterwards nobody could say which change caused what. We rolled back to moving one variable at a time, re-ran three times, and only then did the curve settle. Tedious, but not skippable.

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

1 comments

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

170

This is the post detail page /en/c/edge-computing-resources/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 →