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

Edge Computing · Resources · Ten edge-computing-resources anti-patterns — how many are you guilty of?

336
ECr/edge-computing-resources·posted by li_ming·2 days agoPostmortemLocked

Ten edge-computing-resources anti-patterns — how many are you guilty of?

Some background first. Our setup is edge-computing-resources plus three downstream services, seven figures of daily requests, peaking around nine in the evening.

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.

Performance44%
Maintainability28%
Ecosystem and community17%
Hiring difficulty11%

571 votes total

46 comments

46 comments

M
Mmike_xuMod·just now

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.

506
Llinlin·28 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.

466
Mmike_xu·2 hours agoedited

There is actually a simpler fix that needs no architecture change: move this check up to the gateway and the problem disappears. The cost is one extra lookup at the gateway.

458
Sswoole_lee·2 days ago

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

383
Kkite·1 hour ago

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

372
Llinlin·just nowedited

Can you give a minimal reproduction? I ran it locally for ten minutes and could not reproduce on macOS with the latest version.

362
Mmike_xu·12 minutes ago

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".

298
Llinlin·28 minutes ago

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

265
Rrase·just now

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

118
Ddev_zhou·2 days ago

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

88
Zzhu_zongOP·2 days ago

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

89
Hhuang_ke·1 hour ago

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

27
Aalice_dev·12 minutes ago

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

20
Kkite·just nowedited

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".

227
Kkernel_panic·2 days 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.

447
Bbob_chen·2 days 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.

478
Sswoole_leeOP·2 days ago

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

32
Aalice_dev·1 hour 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.

11
WwinterOP·2 days ago

There is actually a simpler fix that needs no architecture change: move this check up to the gateway and the problem disappears. The cost is one extra lookup at the gateway.

99
Zzhou_yi·2 days ago

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

1
Hhuang_ke·2 hours ago

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

119
Hhuang_keMod·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.

270
Wwinter·2 days agoedited

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

245
Cchen_dev·yesterday

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

51
Oops_wangMod·2 days 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.

37
Nnikic·28 minutes ago

This matches what we see in production. We only hit it past 3k QPS; the earlier load tests showed nothing — the test traffic was too clean, with no long-tail requests.

305
Rran_bo·2 days ago

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

250
Zzhou_yiOP·2 days ago

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

178
Nnikic·just now

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

122
Llinlin·2 days ago

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

217
Lli_ming·2 days ago

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

107
Lli_mingOP·3 minutes ago

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

1
Wwinter·just now

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

15
Kkernel_panicOP·2 days agoedited

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

471
Llinlin·5 hours ago

There is actually a simpler fix that needs no architecture change: move this check up to the gateway and the problem disappears. The cost is one extra lookup at the gateway.

21
Kkernel_panic·5 hours 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.

10
Hhuang_ke·2 hours 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.

88
Sswoole_lee·1 hour 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.

10
Llinlin·28 minutes 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.

274
WwinterOP·2 days ago

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

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

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

1
Rrase·2 days ago

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

1
Ttang_hao·2 days ago

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

102
Kkite·1 hour ago

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

195
Zzhu_zong·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.

15

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