Benchmark: Map (Native vs Ramda vs Lodash vs Lodash/fp vs Immutable)

HTML Preparation code:

<script src="//cdnjs.cloudflare.com/ajax/libs/ramda/0.25.0/ramda.min.js"></script>
<script src='https://cdn.jsdelivr.net/g/lodash@4(lodash.min.js+lodash.fp.min.js)'></script>
<script type='text/javascript' src='https://cdnjs.cloudflare.com/ajax/libs/immutable/3.8.2/immutable.min.js'></script>

Script Preparation code:

var fp = _.noConflict();
function double(n) {
	return n*2;
}
var data = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30];

Tests:

Ramda.map
R.map(double, data);
Array.prototype.map
data.map(double);
lodash.map
_.map(data, double);
Immutable.map
Immutable.fromJS(data).map(double)
lodash/fp.map
fp.map(double)(data)

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Ramda.map
Array.prototype.map
lodash.map
Immutable.map
lodash/fp.map

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated 27 days ago):

LLMs can make mistakes. Check important info.

Let's dive into the world of JavaScript microbenchmarks.

**What is being tested?**

The benchmark measures the speed of four different approaches to apply a transformation function (`double`) to an array of numbers (`data`). The approaches are:

1. **Ramda.map**: A functional programming library that provides a `map` function.
2. **Array.prototype.map**: The built-in `map` method of JavaScript arrays.
3. **Lodash.map**: A utility library that provides a `map` function, aliased as `_`.
4. **Immutable.map**: A functional programming library that provides a `map` function for immutable data structures.

**Options comparison**

The benchmark compares the performance of these four approaches:

* **Ramda.map**: Uses Ramda's `map` function to apply the transformation.
* **Array.prototype.map**: Uses the built-in `map` method of JavaScript arrays.
* **Lodash.map**: Uses Lodash's `_map` function (aliased as `_`) to apply the transformation.
* **Immutable.map**: Uses Immutable's `map` function to apply the transformation.

**Pros and cons of each approach**

1. **Ramda.map**:
	* Pros: Designed for functional programming, easy to use, and optimized for performance.
	* Cons: Requires an additional library (Ramda).
2. **Array.prototype.map**:
	* Pros: Built-in and efficient, no additional libraries required.
	* Cons: Not designed for functional programming, may have lower performance due to the overhead of JavaScript's array methods.
3. **Lodash.map**:
	* Pros: Easy to use, provides a simple and straightforward API.
	* Cons: Requires an additional library (Lodash), and the `_map` function is not as optimized as Ramda's `map`.
4. **Immutable.map**:
	* Pros: Designed for functional programming, immutable data structures can be beneficial in certain scenarios.
	* Cons: Requires an additional library (Immutable), and may have higher overhead due to the immutability.

**Other considerations**

* The benchmark uses a fixed input size (`data`) and transformation function (`double`), which may not accurately represent real-world use cases.
* The benchmark runs on a specific browser (Chrome 115) and operating system (Mac OS X 10.15.7), which may not be representative of other browsers or systems.

**Library and syntax explanation**

* **Ramda**: A functional programming library for JavaScript, providing various higher-order functions like `map`, `filter`, and `reduce`.
	+ Purpose: Provide a concise and expressive API for functional programming.
* **Lodash**: A utility library for JavaScript, providing various helper functions like `_` (aliased as `_`) to simplify common tasks.
	+ Purpose: Simplify everyday coding by providing a collection of reusable functions.
* **Immutable**: A library for immutable data structures in JavaScript, providing tools for working with immutable data.
	+ Purpose: Provide a way to work with immutable data structures, making it easier to reason about code and avoid side effects.

**Special JS feature or syntax**

None mentioned.

Latest run results:

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

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

Browser/OS: Chrome 115 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
Ramda.map	1457417.5 Ops/sec
Array.prototype.map	1028448.4 Ops/sec
lodash.map	1631581.8 Ops/sec
Immutable.map	298983.8 Ops/sec
lodash/fp.map	337204.6 Ops/sec

Related benchmarks:

Map (Native vs Ramda vs Lodash vs Lodash/fp vs Immutable) (version: 0)

measures the speed of ramda's map vs Array's native map vs lodash map vs Immutable map

Comparing performance of: Ramda.map vs Array.prototype.map vs lodash.map vs Immutable.map vs lodash/fp.map

Created: 6 years ago by: Guest

Jump to the latest result

Ramda.map

Array.prototype.map

lodash.map

Immutable.map

lodash/fp.map

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated 27 days ago):