Edge Computing · Resources · Built a visual debugging panel for edge-computing-resources over the weekend

22
ECr/edge-computing-resources·posted by bob_chen·1 hour agoOpen source

Built a visual debugging panel for edge-computing-resources over the weekend

Short version: edge-computing-resources 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.

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.

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

37 votes total

2 comments

2 comments

M
Oops_wang·3 minutes agoedited

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

362
Kkite·12 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.

43

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