Benchmark: Regexp test VS array.every and includes

Script Preparation code:

const keywords = ['some', 'strings'];
const regex = new RegExp(keywords.join("|"), "i");
const string = "Some guitars don't have a lot of strings on them.";

Tests:

Includes
const keywords = ['some', 'strings']; const string = "Some guitars don't have a lot of strings on them."; keywords.every(str => string.toLowerCase().includes(str.toLowerCase()));
Regex.test
const keywords = ['some', 'strings']; const regex = new RegExp(keywords.join("|"), "i"); const string = "Some guitars don't have a lot of strings on them."; regex.test(string);

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Includes
Regex.test

Fastest: N/A

Slowest: N/A

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

LLMs can make mistakes. Check important info.

Let's dive into the world of JavaScript microbenchmarks!

**Benchmark Description**

The benchmark compares two approaches to test whether a string contains specific keywords: using `Array.prototype.every()` and using a regular expression (`RegExp`). The goal is to determine which approach is faster.

**Options Compared**

There are two main options being compared:

1. **`Array.prototype.every()`**: This method checks if every element in the array passes the provided test function. In this case, it's used to check if each keyword is present in the string (case-insensitive).
2. **Regular Expression (`RegExp`)**: A regular expression can be used to match a pattern in a string. Here, the regular expression is created by joining the keywords with `|` (the "or" operator), and the `i` flag at the end makes it case-insensitive.

**Pros and Cons of Each Approach**

1. **`Array.prototype.every()`**:
	* Pros:
		+ Easy to understand and implement.
		+ Can be more intuitive for developers familiar with array methods.
	* Cons:
		+ Creates an array of keyword lowercase strings, which can lead to extra overhead.
		+ May not be as efficient for very large arrays or long strings.
2. **Regular Expression (`RegExp`)**:
	* Pros:
		+ More efficient than `Array.prototype.every()` because it only scans the string once.
		+ Can be more flexible and powerful for pattern matching.
	* Cons:
		+ Requires a better understanding of regular expressions to implement correctly.
		+ May not be as easy to understand or debug for developers unfamiliar with regex.

**Library**

There is no explicit library used in this benchmark. However, `Array.prototype.every()` relies on the array data structure, which is a fundamental concept in JavaScript.

**Special JS Feature/Syntax**

None mentioned explicitly. No special JavaScript features or syntax are being tested in this benchmark.

**Other Alternatives**

For larger strings or more complex pattern matching, other approaches like using `String.prototype.includes()` with multiple arguments (to check for all keywords at once) might be faster than using regular expressions. Additionally, some libraries like `regex-escape` or `regex-util` provide optimized functions for creating and working with regular expressions.

Keep in mind that the choice of approach depends on the specific use case and performance requirements.

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/116.0.0.0 Safari/537.36 Edg/116.0.1938.81

Browser/OS: Chrome 116 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
Includes	5645572.0 Ops/sec
Regex.test	1796161.4 Ops/sec

Related benchmarks:

Regexp test VS array.every and includes (version: 0)

Comparing performance of: Includes vs Regex.test

Created: one year ago by: Guest

Jump to the latest result

Includes

Regex.test

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):