All issues

Cold-start latency regression on edge nodes after v2.1#503

New issue
Open
KWKwame Okoyecommented 3d ago

Describe the bug

Cold-start latency regression on edge nodes after v2.1 — surfaces on atlas-edge in the critical-priority path. The full reproduction is below, along with the workaround we use in staging.

Reproduce

  • Clone ln-dev7/atlas-edge at the tip of main.
  • Run the smoke suite: pnpm test --workspace atlas-edge.
  • Notice the test for the affected contract flakes within the first 50 iterations.

Expected behavior

The contract should hold deterministically across the full matrix — staging, production, and the local dev runtime.

Environment

  • node 22.x
  • pnpm 9.x
  • OS: macOS 15.2 (also reproduced on Linux 6.x)

Labels: performance, bug

KWKwame Okoyecommented 3d ago

Bumping priority — three customers hit this last week, two of them on the enterprise tier.

LNLNcommented 3d ago

Re-reading the spec, I think the right contract is the one in the bug report, not the one we're shipping. Going to open a small PR.

KWkwame-okoyeself-assigned this3d ago
KWkwame-okoyeadded the labelperformance3d ago
KWkwame-okoyeadded this to the milestonev2.23d ago
KWKwame Okoyecommented 3d ago

Closing in favor of #605 — same root cause, same approach, and that branch is further along.

LNln-dev7added a commit that references this issuefix(atlas): guard the regression surfaced in #50303089222d ago
LNLNcommented 2d ago

I've seen this too. I'll fix.

KWkwame-okoyementioned this in#5552d ago

Add a comment

M↓Markdown is supported