Bun benchmark gained’t substitute Node but. It’s quick, although.

What’s your present JavaScript runtime, and why is it Node.js? However have you ever heard there’s a brand new answer on the town? Bun is a local code bundler, transpiler, and job runner with a built-in npm shopper. The creators promised to meet our want for pace and prioritized Bun’s efficiency over all different options. On this article, I’ll present you begin an current Node.js mission on this new JavaScript runtime and examine if Bun is absolutely the quickest on the market.

First issues first, what’s JavaScript runtime?

A runtime surroundings is the place your program might be executed. You are able to do it:

  • by JavaScript engine built-in browser (V8 developed by the Chromium Mission for Google Chrome)
  • on server environments (similar to Node.js or Bun) that are de-facto implementations of a “browser” operating on the server.

There are few Javascript runtimes available on the market. As of writing this text, the highest three appear to be this. 


Node.js – the most well-liked (by GitHub stars), the oldest, however above all “the primary one”. Earlier than Node, JS existed solely within the browser, so we’ve got rather a lot to be thankful for. 

At The Software program Home, we run our JS functions on Node.js, because it’s a longtime JS execution surroundings. In reality, it’s the one one supported by AWS Lambda and GCP Capabilities.

Should you’re right here, you undoubtedly know Node in and out, so let’s transfer on.


In second place there’s Deno. We’ve already made some makes an attempt to check out Deno and we actually gave it an opportunity. Sadly, we didn’t discover it convincing sufficient to maneuver to this nonetheless barely immature JS runtime. 

Learn extra about our Deno experiences:

However the reality was a reality – a contest appeared. We have now been curious ever since if one thing else than Node.js and Deno would fulfill JS builders’ hopes for tremendous quick JS functions.

After which Bun was baked in Oven!

What’s Bun?

As of writing, the third place is occupied by recent and crisp Bun – the latest and fastest-growing JS runtime. Bun attracted quite a lot of consideration when it gained $7 million in funding in August 2022. 

All the Bun mission focuses on efficiency and being an all-in-one instrument (runtime, bundler, package deal supervisor, transpiler). 

Within the “conventional” Node.js, you want the mixed energy of a few instruments to attain the identical targets: npm, Webpack, and so on.

How is Bun presupposed to be quicker than Node? 

Aiming to spice up its efficiency, the Bun workforce wrote it from scratch in Zig, a low-level C different. The browser engine operating JS code in Bun is predicated on JavaScript Core – the JS engine inside Safari that’s thought of quicker than Node’s V8, the engine inside Chromium. 

Bun ships and the event workforce declare it’s quicker due to an unlimited period of time spent profiling, benchmarking, and optimizing issues. The final theme: Zig’s low-level management over reminiscence and lack of hidden management circulation makes it a lot simpler to put in writing quick software program.

bun fast benchmark for server side rendering react app (linux), comparison with node.js and deno
Supply: bestofjs.org

In abstract, Bun creators declare that it serves 4 instances extra requests per second and packages are put in 30 instances quicker than by npm.

bun vs node

My time with Bun

After studying Bun creator’s assurances and group dialogue, I assumed “that’s some huge claims”. I used to be curious if what they are saying is true. Is Bun actually that quick? Truly quicker than Node.js? 

I’ve already seen a couple of benchmarks (and different tech options for that matter) that promised the world however hardly delivered, so I used to be not going to interchange Node with none exhausting information. So I’ve finished what’s wanted to be finished: set up Bun and get the quantity with some efficiency testing.

Let’s transfer on to implementation.

Find out how to run your Categorical app with Bun?

In an effort to take a look at Bun, I used The Software program Home’s home made (or ought to I slightly say “officemade”) Categorical Boilerplate. This boilerplate is extremely scalable and focuses on efficiency and greatest practices boilerplate code for Node.js and TypeScript apps.

If you wish to begin your Node.js initiatives even quicker, right here’s an in depth overview of the TSH-original boilerplate:

So, to run Bun you want to comply with these steps:

$ curl https://bun.sh/set up | bash

$ export BUN_INSTALL="$HOME/.bun"

$ export PATH="$BUN_INSTALL/bin:$PATH"

$ cd repo

$ cp docker-compose.override.yml.dist docker-compose.override.yml

$ cp .env.dist .env

$ bun i

$ bun run docker-build

$ bun run watch

$ bun run begin

As you’ll be able to see,  runs with no adjustments. 

Let’s examine Bun and Node!

1. Package deal set up time

The primary take a look at we’re operating is package deal set up time. We did a easy take a look at, to simulate real-life workflow.

  • Npm run put in 1273 packages in 23 seconds, 
  • Bun run put in 1003 in 15,6 seconds.

bun dev test - same code different results


*Disclaimer: Bun certainly is 32% quicker, however the execution time it’s not as quick as Bun’s creator promised

2. Docker picture

The second factor to match is constructing the primary docker picture.

test bun vs node


Utilizing Bun doesn’t appear to have an effect on Docker image-building time.

3. App-builder

Take a look at quantity three will verify how Bun and npm cope with beginning app-builder.

bun install


The distinction is so minimal that there’s no purpose to modify to Bun on objective.

4. Utility begin time

The fourth factor we examine is the applying begin time.

bun production ready package manager


…however once more, the distinction is negligible.

Now, crucial. Is Bun quicker than Node?

Under, we’re testing easy get endpoint /well being 

The instrument we use on this take a look at is WRK – a contemporary HTTP benchmarking instrument able to producing important load when run on a single multi-core CPU.

In these exams, we’re utilizing Node 16.15.0 and Bun 0.2.1. 

Take a look at 1. 10000 connections in 60 seconds with a variable variety of threads

creating http requests


Okay, honest sufficient. How about we tweak it up a bit with totally different parameters? 

10 threads in 60 seconds, with a variable variety of connections

bun & node compatibility with more features

As you’ll be able to see, relying on the variety of connections and the variety of threads the outcomes are related. However usually, Node.js is quicker. So…


Do you have to transfer from Node to Bun? Most likely not

I’ve acquired some excellent news and unhealthy information.

The unhealthy information: Bun isn’t going to be a drop-in alternative for Node anytime quickly

For this text, I’ve used an current Node.js software. I can let you know that it’s not value operating your secure Node app on Bun. Though there’s large potential and room for growth – for now, it’s simply too immature. Bun’s nonetheless new has no full documentation, and varied errors could happen throughout implementation. Additionally, I’m fairly certain that within the foreseeable future it gained’t be helpful in serverless options utilizing AWS Lambda, or Google Cloud Capabilities (as of writing, Node.js is the one supported surroundings). It would take a while for Bun.js to develop and change into a expertise that we are able to use in business initiatives. At current, Bun’s tiny wins in pace exams gained’t compensate for the time misplaced in the event you run into surprising errors. 

Should you began a brand new self-hosted early-stage mission you should utilize Bun.js from the start and optimize it for working with Bun. Then, certain go for it!

A small comfort for the Bun workforce whereas they’re in all probability enhancing their answer – you have already got the sweetest brand within the recreation. Simply look once more at how cute it’s! 

is bun faster than node.js and other tools?

The excellent news: Node.js might be pressured to innovate

Now, Node.js has not just one however two potential rivals available on the market. I guess the Node workforce might be extra “motivated” to extend their product’s efficiency as a lot as they’ll. 

I imagine that these applied sciences will probably coexist within the ecosystem slightly than one displacing the opposite, very like a number of JDK distributions have spawned within the Java world, one being chosen above one other largely for licensing causes. However figuring out the fast-changing world of JavaScript, quickly a brand new expertise will seem with the intention to take over the market.

Michał Mońka

Michał Mońka

Node.js Junior Developer

Information-hungry Node.js developer. In his free time, Michał travels and engages in varied sports activities disciplines, largely climbing.


Leave a Reply

Your email address will not be published.