Benchmark: Lodash Uniq vs Javascript Set, smaller set

HTML Preparation code:

<script src="https://cdn.jsdelivr.net/npm/lodash@4.17.5/lodash.min.js"></script>

Script Preparation code:

var firstEqual = [];
var secondEqual = [];

for (var i=0; i<=100000; i++) {
  firstEqual.push(i);
  secondEqual.push(i);
}

var arrayToDedup = [...firstEqual, ...secondEqual];

Tests:

Lodash Uniq
_.uniq(arrayToDedup);
Javascript Set
[...new Set(arrayToDedup)]

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Lodash Uniq
Javascript Set

Fastest: N/A

Slowest: N/A

Latest run results:

No previous run results

This benchmark does not have any results yet. Be the first one to run it!

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 JavaScript microbenchmarks.

**Benchmark Definition**

The benchmark is designed to compare two approaches for removing duplicates from an array: using Lodash's `uniq` function and using a built-in JavaScript `Set` object.

**Script Preparation Code**

The script preparation code creates two arrays, `firstEqual` and `secondEqual`, both containing 100,000 elements with increasing integer values. The code then combines these two arrays into a single array, `arrayToDedup`.

**Html Preparation Code**

The HTML preparation code includes a link to the Lodash library (version 4.17.5) from a CDN.

**Individual Test Cases**

There are two test cases:

1. **Lodash Uniq**: The benchmark definition uses Lodash's `uniq` function to remove duplicates from the `arrayToDedup` array.
2. **Javascript Set**: The benchmark definition uses a built-in JavaScript `Set` object to remove duplicates from the `arrayToDedup` array.

**Pros and Cons**

Here are some pros and cons of each approach:

* **Lodash Uniq**:
	+ Pros:
		- Easy to use and understand, especially for developers familiar with Lodash.
		- Provides a clear and consistent API for removing duplicates.
	+ Cons:
		- Requires including the Lodash library in the HTML code, which may add unnecessary size and latency to the benchmark.
		- May have overhead due to the library's functionality and dependencies.
* **Javascript Set**:
	+ Pros:
		- Built-in and widely supported by modern browsers, so no additional libraries are required.
		- Efficient and lightweight compared to using a library like Lodash.
	+ Cons:
		- Requires a basic understanding of JavaScript sets and their usage.
		- May not be as intuitive or user-friendly for developers without prior experience with sets.

**Other Considerations**

When choosing between these two approaches, consider the trade-offs between ease of use, performance, and size. If you prioritize speed and efficiency, using a `Set` object may be a better choice. However, if you prefer a more straightforward and intuitive API, Lodash's `uniq` function might be a better fit.

**Special JavaScript Feature**

There is no special JavaScript feature or syntax being used in this benchmark. Both test cases rely on standard JavaScript functionality and built-in objects (Lodash for the `uniq` function).

**Alternatives**

If you're interested in exploring alternative approaches, here are a few options:

* **Array.prototype.filter()**: You can use the `filter()` method to remove duplicates from an array, like this: `[...new Array(100000).keys()].filter(x => new Set([x, x + 1]).has(x))`.
* **lodash-uniqby()**: If you want a more flexible approach, you can use Lodash's `uniqby` function, which removes duplicates based on a custom key.
* **Other libraries and approaches**: There are other JavaScript libraries and approaches available for removing duplicates from arrays, such as the `unique()` function in the `pako` library or using a combination of `filter()` and `reduce()`.

Related benchmarks:

Lodash Uniq vs Javascript Set, smaller set (version: 0)

Comparing performance of: Lodash Uniq vs Javascript Set

Created: 5 years ago by: Guest

Jump to the latest result

Lodash Uniq

Javascript Set

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

No previous run results

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