Benchmark: Unit Converters Benchmark

HTML Preparation code:

<script src="//cdnjs.cloudflare.com/ajax/libs/require.js/2.1.11/require.min.js"></script>

Script Preparation code:

var _function = new Function('distance', "return distance * 0.621371192237334");

var _mathjs = undefined;
require(['https://cdnjs.cloudflare.com/ajax/libs/mathjs/13.0.3/math.min.js'], function(lib) {
  mathjs = lib;
});

var _convert = undefined;
require(['https://cdn.jsdelivr.net/npm/convert@5/dist/index.js'], function(lib) {
  _convert = lib;
});

var _unitsConverter = undefined;
require(['https://cdn.jsdelivr.net/npm/units-converter@1.0.3/dist/umd/index.min.js'], function(lib) {
  _unitsConverter = lib;
});

var _jsQuantities = undefined;
require(['https://cdnjs.cloudflare.com/ajax/libs/js-quantities/1.8.0/quantities.min.js'], function(lib) {
  _jsQuantities = lib;
});

Tests:

convert function
_function(100);
mathjs
mathjs.unit(100, "km").toNumber('mile')
units-converter
_unitsConverter.length(100).from("km").to('mi').value
js-quantities
_jsQuantities(100, 'km').to('mi').scalar
convert
_convert.convert(100, "km").to('miles')

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
convert function
mathjs
units-converter
js-quantities
convert

Fastest: N/A

Slowest: N/A

Latest run results:

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

User agent: Mozilla/5.0 (Linux; Android 10; SAMSUNG SM-J810G) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/16.0 Chrome/92.0.4515.166 Mobile Safari/537.36

Browser/OS: Chrome Mobile 92 on Android

View result in a separate tab

Test name	Executions per second
convert function	969722.3 Ops/sec
mathjs	14511.2 Ops/sec
units-converter	26372.3 Ops/sec
js-quantities	9847.1 Ops/sec
convert	424453.6 Ops/sec

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

LLMs can make mistakes. Check important info.

Let's dive into the world of MeasureThat.net, where JavaScript microbenchmarks come to life.

**Benchmark Definition**

The provided JSON represents a benchmark for unit conversion. The benchmark definition is created using the `Function` constructor in JavaScript. It defines a function that takes a distance value as an argument and returns the equivalent distance in miles by multiplying it with a conversion factor (0.621371192237334).

The script preparation code includes four main libraries:

1. **Math.js**: A mathematics library that provides various mathematical functions, including unit conversions.
2. **Convert**: A library specifically designed for unit conversions.
3. **Units Converter**: Another library for unit conversions.
4. **Js Quantities**: A library for working with physical quantities and units.

**Options Compared**

The benchmark compares the performance of four different approaches:

1. Using the `Function` constructor to create a custom conversion function (`convert function`)
2. Utilizing Math.js's `unit()` function for unit conversions (`mathjs`)
3. Leveraging Units Converter's API for unit conversions (`units-converter`)
4. Employing Js Quantities' `to()` method for unit conversions (`js-quantities`)

**Pros and Cons**

Here's a brief overview of each approach:

1. **Custom Function (convert function)**:
	* Pros: Provides direct control over the conversion logic, allowing for potential optimizations.
	* Cons: May require more boilerplate code and is specific to this benchmark.
2. **Math.js (`mathjs`)**:
	* Pros: Offers a wide range of mathematical functions, including unit conversions, with minimal code changes.
	* Cons: Requires an additional library, which may introduce performance overhead.
3. **Units Converter (`units-converter`)**:
	* Pros: Designed specifically for unit conversions, providing a simple and efficient API.
	* Cons: May not offer the same level of customization as the custom function approach.
4. **Js Quantities (`js-quantities`)**:
	* Pros: Provides a convenient and expressive way to work with physical quantities and units.
	* Cons: May introduce performance overhead due to its additional features.

**Other Considerations**

When choosing an approach, consider the following factors:

* Performance: Which library provides the best performance for unit conversions?
* Customization: Do you need fine-grained control over the conversion logic?
* Code size and complexity: How much boilerplate code is required for each approach?

**Alternatives**

If you're not satisfied with these four options, consider the following alternatives:

1. **Built-in JavaScript functions**: Explore using built-in JavaScript functions like `Number()` or `parseFloat()` for simple conversions.
2. **Other libraries**: Research other libraries specifically designed for unit conversions, such as `units.js` or `quantities.js`.
3. **Domain-specific languages (DSLs)**: Investigate using DSLs like MathExpression or ExprJS for more complex mathematical computations.

In conclusion, the choice of approach depends on your specific needs and priorities. By understanding the pros and cons of each option, you can make an informed decision that balances performance, customization, and code complexity.

Related benchmarks:

Unit Converters Benchmark (version: 0)

Comparing performance of: convert function vs mathjs vs units-converter vs js-quantities vs convert

Created: one year ago by: Registered User

Jump to the latest result

convert function

mathjs

units-converter

js-quantities

convert

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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