1. X
  2. Bun
Log inSign up
Bun
4,036 posts
Image
user avatar
Bun
@bunjavascript
Bun is a fast, all-in-one toolkit for installing, bundling, running and testing JavaScript & TypeScript. To install: `npm i -g bun`
bun.com
Joined July 2022
7
Following
80.5K
Followers
AffiliatesAffiliatesRepliesRepliesMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • Pinned
    user avatar
    Bun
    @bunjavascript
    Dec 2, 2025
    Bun is joining Anthropic!
    Image
    Bun is joining Anthropic
    From bun.com
    4.5M
  • user avatar
    Bun
    @bunjavascript
    14h
    In the next version of Bun We fixed a GC retention cycle that made Next.js App Router SSR leak memory when a page called fetch()
    Next.js 16 · App Router · next start. The SSR memory leak is gone in Bun v1.4.” Subtitle: “4,000 server-rendered pages: Bun v1.4 settles at 238 MB, under Node’s 410 MB. Bun v1.3.14 climbed to 1,983 MB and kept going.” A line chart of server memory (RSS) against requests served, 0 to 4,000, then a dashed tail to the value after 5 seconds idle. Bun v1.3.14 rises steadily to a 1,983 MB peak and settles at 1,901 MB; Node v26.5 flattens around 400 MB and settles at 410 MB; Bun v1.4 stays flat near 300–350 MB and settles at 238 MB. Footer: stock create-next-app (Next 16.2.3, React 19.2) with the bug report’s page — a React.cache-wrapped fetch(…, { cache: “no-store” }) in a dynamic route; 4,000 unique URLs at 50 concurrent; server RSS sampled from /proc every 200 requests; product API is a separate Node process; Linux x64; bun 1.4.0-canary f91d5c95c, bun 1.3.14, node 26.5.0.
    26K
  • user avatar
    Bun
    @bunjavascript
    15h
    In the next version of Bun Saving streaming file uploads to disk via Bun.write uses 35x less memory compared to Bun v1.3.14
    Benchmark card titled “Saving 5,000 uploads to disk · 2 MB each — same Hono app, three runtimes.” Subtitle: “Bun v1.4 uses 35× less memory than v1.3.14 and takes uploads at 1.65× Node’s requests per second.” Horizontal bar chart of peak memory (max RSS of the server process, shorter is better): Bun v1.4 316 MB, Bun v1.3.14 11,142 MB (bar fills the track), Node v26.5 213 MB. Smaller figures below: requests per second — Bun v1.4 999, Bun v1.3.14 552, Node 604; CPU time — Bun v1.4 16.3 s, Bun v1.3.14 20.8 s, Node 19.5 s. Route under test: app.post(”/upload”, async (c) => { await Bun.write(path, c.req.raw); return c.text(“ok”) }), with a note that Node saves it with await pipeline(Readable.fromWeb(c.req.raw.body), createWriteStream(path)). Footer: oha -c 100 -n 5000 -m POST -D 2mb.bin, same Hono 4.12 app on each runtime, each saving the body its idiomatic way, Linux x64, GNU time -v, median of 5 runs; bun 1.4.0-canary f91d5c95c, bun 1.3.14, node 26.5.0.
    17K
  • user avatar
    Bun
    @bunjavascript
    16h
    In the next version of Bun Proxying file uploads uses 10x less memory than in v1.3.14
    Benchmark card titled “Relaying 300 uploads to storage · 20 MB each — same Hono app, three runtimes.” Subtitle: “Bun v1.4 matches Node’s memory at a third of the CPU — v1.3.14 needed 11× more RAM.” Horizontal bar chart of peak memory (max RSS of the server process, shorter is better): Bun v1.4 205 MB, Bun v1.3.14 2,259 MB (bar fills the track), Node v26.5 203 MB. Smaller figures below: CPU time — Bun v1.4 5.0 s, Bun v1.3.14 8.0 s, Node 13.9 s; wall clock — 31.5 s, 31.5 s, 31.6 s (storage sets the pace). Route under test: app.post(”/relay”, (c) => fetch(bucketUrl, { method: “PUT”, body: c.req.raw.body, duplex: “half” })). Footer: oha -c 100 -n 300 -m POST -D 20mb.bin, same Hono 4.12 app on each runtime, storage endpoint capped at 200 MB/s with tc, Linux x64, GNU time -v, median of 5 runs; bun 1.4.0-canary f91d5c95c, bun 1.3.14, node 26.5.0.
    13K
  • user avatar
    Bun
    @bunjavascript
    16h
    In the next version of Bun Several bugs involving backpressure propagation have been fixed
    Benchmark card titled “Proxying 2,000 downloads · 2 MB each — same Hono app, three runtimes.” Subtitle: “Bun v1.4 holds half the memory of Node while serving 2× the requests per second.” A horizontal bar chart of peak memory (max RSS of the server process, shorter is better): Bun v1.4 171 MB, Bun v1.3.14 245 MB, Node v26.5 326 MB. Below, smaller figures: requests per second — Bun v1.4 868, Bun v1.3.14 948, Node 443; CPU time — Bun v1.4 3.9 s, Bun v1.3.14 3.6 s, Node 6.3 s. The route under test is one line: app.get(”/proxy”, (c) => fetch(originUrl)). Footer: oha -c 100 -n 2000, same Hono 4.12 app on each runtime, origin serves at line rate, Linux x64, GNU time -v for max RSS and CPU, median of 5 runs; bun 1.4.0-canary f91d5c95c, bun 1.3.14, node 26.5.0.
    14K
  • See @bunjavascript's full profile

    Sign up
    Log in
Advertisement
Advertisement