WhatBrokeToday
GTA 6FAQ
Bun

Bun AOT Compiler Rewrite Regression Slows Map/Set Iteration and Array Reads

medium

Is it fixed? Not yet.

Ongoing since Nov 8, 21:48 UTC. First reported Nov 8, 21:48 UTC.

What happened

Runtime performance for bun build --compile --aot executables dropped significantly following the AOT compiler rewrite in PR #47942. Common operations such as Map and Set iteration, Map.get/Map.has lookups, and array reads are now 1.5 to 4x slower compared to the previous canary version.

What caused it?

The AOT compiler rewrite merged in PR #47942 introduced performance regressions affecting common runtime operations like Map/Set iteration, lookups, and array reads.

No verified workaround yet

None of the linked reports describe a mitigation. This page updates when one appears.

Timeline

  1. Investigating(current)
  2. Workaround available(upcoming)
  3. Resolved(upcoming)
  1. First report on GitHub issue

    AOT: Map/Set iteration, Map.get and array reads are 2-4x slower since the compiler rewrite (#47942)

    Source

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    AOT: Map/Set iteration, Map.get and array reads are 2-4x slower since the compiler rewrite (#47942)(opens GitHub issue in a new tab)

    Summary Between 7ca0042d3 (last canary with the old AOT compiler) and 2596ac5d3 (the merge of #47942, the AOT rewrite), the runtime speed of several very common operations dropped sharply in bun build --compile --aot executables: Map / Set iteration: 3.5-4x slower than the old AOT Map.get / Map.has: 1.5-2.5x slower than the old AOT, and slower than --no-aot (JIT) reading array[i].field and number[]: ~1.5-1.8x slower a real-world exact search (below): 2.5-2.7x slower than the old AOT, and ~1.9x…

    by yoch 0upvotes 1comments

FAQ

What happened in the Bun issue?

Runtime performance for bun build --compile --aot executables dropped significantly following the AOT compiler rewrite in PR #47942. Common operations such as Map and Set iteration, Map.get/Map.has lookups, and array reads are now 1.5 to 4x slower compared to the previous canary version.

What is affected by the Bun issue?

Bun.

When did the Bun issue start and end?

It started Nov 8, 21:48 UTC and is still ongoing (10 d 6 h so far). This page updates as it develops.

How do I get alerts for Bun?

Subscribe to the Bun RSS feed for every new Bun incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Bun is down. Bun feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.