Benchmark: JS BigInt big number performance v2

Script Preparation code:

var bigInt1 = 1000000n
var bigInt2 = 50n
var number1 = 1000000
var number2 = 50

Tests:

BigInt
a = bigInt1 b = bigInt2 c = a - b c = a % b c = a * b c = a + b c = a ** b
Number
a = number1 b = number2 c = a - b c = a % b c = a * b c = a + b c = a ** b

Historical Performance Data aggregated from 343 community runs

Desktop Results:

Chrome 195 runs

Number

813K/s

BigInt

689K/s

Fastest: Number (1.2x faster)

View exact numbers

✓ Number: 813,161 ops/sec
• BigInt: 688,866 ops/sec

Firefox 76 runs

Number

19.7M/s

BigInt

1.2M/s

Fastest: Number (16.0x faster)

View exact numbers

✓ Number: 19,670,554 ops/sec
• BigInt: 1,230,319 ops/sec

Safari 14 runs

Number

960K/s

BigInt

683K/s

Fastest: Number (1.4x faster)

View exact numbers

✓ Number: 960,096 ops/sec
• BigInt: 682,615 ops/sec

Mobile Results:

Chrome 41 runs

Number

532K/s

BigInt

396K/s

Fastest: Number (1.3x faster)

View exact numbers

✓ Number: 532,289 ops/sec
• BigInt: 395,716 ops/sec

Firefox 10 runs

Number

20.2M/s

BigInt

687K/s

Fastest: Number (29.4x faster)

View exact numbers

✓ Number: 20,217,652 ops/sec
• BigInt: 687,001 ops/sec

Safari 7 runs

Number

65.0M/s

BigInt

2.7M/s

Fastest: Number (23.9x faster)

View exact numbers

✓ Number: 65,010,196 ops/sec
• BigInt: 2,721,324 ops/sec

Results show median performance across all community submissions. Run this benchmark yourself to verify on your device.

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
BigInt
Number

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: one month ago)

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:152.0) Gecko/20100101 Firefox/152.0

Browser/OS: Firefox 152 on Linux

View result in a separate tab

Number

7.5M/s

BigInt

713K/s

View exact numbers

Test name	Executions per second
✓ Number	7,532,754 Ops/sec
BigInt	712,528 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

LLMs can make mistakes. Check important info.

Let's break down the benchmark and its test cases.

**What is being tested?**

The provided JSON represents a JavaScript microbenchmark that compares the performance of two data types: `Number` and `BigInt`. Specifically, it measures the execution time of various arithmetic operations (addition, subtraction, multiplication, division, exponentiation) on both data types for large numbers.

**Options compared**

Two options are being compared:

1. **Number**: The traditional JavaScript number type.
2. **BigInt**: A relatively new data type introduced in ECMAScript 2020, designed to support arbitrary-precision integers.

**Pros and Cons of each approach:**

* **Number**:
	+ Pros:
		- Wide browser support
		- Simple implementation (no need for additional libraries)
	+ Cons:
		- Limited precision, which can lead to rounding errors and performance issues with very large numbers.
		- May exhibit slower performance due to the need for approximation or rounding.
* **BigInt**:
	+ Pros:
		- Arbitrary-precision support, eliminating rounding errors and potential performance bottlenecks.
		- Designed specifically for high-performance arithmetic operations on large integers.
	+ Cons:
		- Requires support from modern browsers (Chrome 129 and above) and engines (e.g., V8 in Chrome).
		- May require additional libraries or workarounds for older browsers.

**Library usage**

The benchmark uses the `BigInt` library to create and manipulate `BigInt` values. However, since this is a built-in JavaScript feature starting from ECMAScript 2020, no external library is necessary.

**Special JS feature or syntax**

The test cases utilize the `n` suffix for BigInt literals, introduced in ECMAScript 2019. This allows you to create arbitrary-precision integers without needing additional libraries or workarounds.

**Other alternatives**

If a browser does not support `BigInt`, you might consider using:

1. Third-party libraries like `big.js` or `decimal.js` that provide similar arithmetic capabilities.
2. Other data types, such as strings or arrays of integers, for smaller numbers.
3. Using a different language or runtime environment that supports arbitrary-precision integers.

Keep in mind that each alternative has its own trade-offs and requirements, so the choice depends on your specific use case and constraints.

JS BigInt big number performance v2 (version: 0)

Compare Number vs BigInt for big numbers

Comparing performance of: `BigInt vs Number`

Created: 4 years ago by: Guest

Go to the latest result

BigInt

Number

Historical Performance Data aggregated from 343 community runs

Desktop Results:

Chrome 195 runs

Firefox 76 runs

Safari 14 runs

Mobile Results:

Chrome 41 runs

Firefox 10 runs

Safari 7 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

JS BigInt big number performance v2 (version: 0)

Compare Number vs BigInt for big numbers

Comparing performance of: BigInt vs Number

Created: 4 years ago by: Guest

Go to the latest result

BigInt

Number

Historical Performance Data aggregated from 343 community runs

Desktop Results:

Chrome 195 runs

Firefox 76 runs

Safari 14 runs

Mobile Results:

Chrome 41 runs

Firefox 10 runs

Safari 7 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

Related benchmarks

Comparing performance of: `BigInt vs Number`