Benchmark: bignumber.js vs. big.js vs. decimal.js (I)

HTML Preparation code:

<!--script src="https://raw.githubusercontent.com/iriscouch/bigdecimal.js/v0.6.1/lib/bigdecimal.js"></script-->
<script src="https://cdnjs.cloudflare.com/ajax/libs/bignumber.js/9.0.1/bignumber.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/big.js/6.0.3/big.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/decimal.js/10.2.1/decimal.min.js"></script>
<!--script src="https://raw.githubusercontent.com/infusion/Fraction.js/v4.0.12/fraction.min.js"></script-->

Tests:

Native
var a = 0.1; var b = 0.2; ((a + b) * b).toString();
Native + toFixed
var a = 0.1; var b = 0.2; ((a + b) * b).toFixed(9);
decimal.js
var a = new Decimal("0.1"); var b = new Decimal("0.2"); a.plus(b).times(b).toString();
big.js
var a = new Big("0.1"); var b = new Big("0.2"); a.plus(b).mul(b).toString();
bignumber.js
var a = new BigNumber("0.1"); var b = new BigNumber("0.2"); a.plus(b).multipliedBy(b).toString();

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Native
Native + toFixed
decimal.js
big.js
bignumber.js

Fastest: N/A

Slowest: N/A

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

LLMs can make mistakes. Check important info.

I'll break down the explanation of the provided JSON data into manageable chunks.

**Benchmark Overview**

The test aims to compare the performance of three libraries for handling decimal arithmetic:

1. **big.js**: A high-performance, JavaScript-based library for precise floating-point calculations.
2. **decimal.js**: A library that provides a simple and consistent API for decimal arithmetic operations.
3. **bignumber.js**: A library designed for large and precise numerical computations.

**Library Descriptions**

* **Big.js**: Developed by Mike McLean, big.js is optimized for speed and performance in JavaScript applications. It uses the IEEE 754 floating-point standard to handle decimal arithmetic.
* **Decimal.js**: Also developed by Mike McLean, decimal.js provides a simple and consistent API for decimal arithmetic operations. It is designed to be easy to use and understand.
* **Bignumber.js**: Developed by Mike McLean as well, bignumber.js is focused on handling large numbers with high precision. It uses a proprietary algorithm for fast calculations.

**Options Comparison**

The test compares the performance of each library in two different scenarios:

1. **Native**: The basic arithmetic operation `((a + b) * b).toString()` without any additional formatting.
2. **Native + toFixed**: The same operation with the addition of `toFixed(9)` for formatting.

**Pros and Cons**

* **big.js**
	+ Pros: High performance, optimized for speed.
	+ Cons: Can be more complex to use due to its proprietary algorithm.
* **decimal.js**
	+ Pros: Simple and consistent API, easy to understand.
	+ Cons: May not be as performant as big.js for large computations.
* **bignumber.js**
	+ Pros: Fast calculations for large numbers with high precision.
	+ Cons: May have higher memory usage due to its proprietary algorithm.

**Other Considerations**

When choosing a library, consider the specific requirements of your project:

* Precision: If you need exact decimal arithmetic, decimal.js might be a better choice. For high-precision calculations, bignumber.js is more suitable.
* Performance: big.js is optimized for speed, making it a good choice if you prioritize performance over ease of use.

**Alternatives**

Other alternatives to these libraries include:

* **Fraction.js**: A library that provides a simple API for handling fractional arithmetic. However, it is not as widely used or supported as the other three libraries.
* **Mathjs**: A library that provides an extensive set of mathematical functions and operations. While not specifically designed for decimal arithmetic, it can be used for this purpose.

In summary, the test provides a comparison of three libraries with different strengths and weaknesses. By understanding the pros and cons of each library, you can choose the best one for your specific project needs.

Latest run results:

Run details: (Test run date: 4 days ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36

Browser/OS: Chrome 130 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
Native	107276800.0 Ops/sec
Native + toFixed	9554594.0 Ops/sec
decimal.js	1289654.6 Ops/sec
big.js	2129370.5 Ops/sec
bignumber.js	1228511.9 Ops/sec

Related benchmarks:

bignumber.js vs. big.js vs. decimal.js (I) (version: 0)

- https://github.com/MikeMcl/bignumber.js/tree/v9.0.0 - https://github.com/MikeMcl/big.js/tree/v5.2.2 - https://github.com/MikeMcl/decimal.js/tree/v10.2.0

Comparing performance of: Native vs Native + toFixed vs decimal.js vs big.js vs bignumber.js

Created: 3 years ago by: Guest

Jump to the latest result

Native

Native + toFixed

decimal.js

big.js

bignumber.js

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

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