Benchmark: Regex v split find str carriage test

Script Preparation code:

var str = 'Abcd efghi\r\nj klmnopqrstuv wxy A\r\nbcd efghij klmnopqrstuv\r\n wxy Abcd efghij k\r\nlmnopqrstuv wxyAbcd efghij klmnopqrstu\r\nv wxy Abcd efghij klmnopqrstuv wxy Abcd efghi\r\nj klmnopqrs\r\ntuv wxy';
var re = new RegExp('\r\n', 'g');

Tests:

Regex
str.match(re)?.length || 0;
Split
str.split('\r\n').length - 1;

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Regex
Split

Fastest: N/A

Slowest: N/A

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

LLMs can make mistakes. Check important info.

Let's break down the benchmark and explain what's being tested.

**Benchmark Overview**

The benchmark measures the performance of two JavaScript functions: `str.match()` with a regular expression, and `str.split()`. The input string `str` contains newline characters (`\r\n`) to simulate a multi-line text.

**Options Compared**

There are two options compared:

1. **Regex**: Using `str.match(re)`, where `re` is the regular expression `\r\n`, which matches any newline character.
2. **Split**: Using `str.split('\r\n')`, which splits the string into an array of substrings using the specified separator.

**Pros and Cons**

* **Regex**:
	+ Pros: Can match complex patterns, including multi-line text, with a single regular expression.
	+ Cons: Can be slower due to the overhead of compiling and executing the regular expression.
* **Split**:
	+ Pros: Faster and more straightforward, as it relies on a simple string splitting operation.
	+ Cons: May not work correctly if the input string contains non-ASCII newline characters.

**Library Used**

None is explicitly mentioned in the benchmark definition. However, it's likely that the `RegExp` object is used under the hood to create the regular expression `\r\n`.

**Special JS Feature/Syntax**

There are no special JavaScript features or syntaxes being tested in this benchmark. The tests focus on basic string manipulation operations.

**Other Alternatives**

If you were to reimplement this benchmark, here are alternative approaches you could consider:

* Using `String.prototype.replace()` with a callback function to replace all newline characters.
* Using a library like `pcre.js` for regular expression matching and replacement.
* Using a native JavaScript method like `TextEncoder` to handle multi-line text encoding.

Keep in mind that these alternatives might have different performance characteristics and may not be suitable for all use cases.

Latest run results:

Run details: (Test run date: 2 years ago)

User agent: Mozilla/5.0 (Linux; Android 13; Pixel 4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Mobile Safari/537.36

Browser/OS: Chrome Mobile 106 on Android

View result in a separate tab

Test name	Executions per second
Regex	1293395.0 Ops/sec
Split	2782862.5 Ops/sec

Related benchmarks:

Regex v split find str carriage test (version: 0)

Comparing performance of: Regex vs Split

Created: 2 years ago by: Guest

Jump to the latest result

Regex

Split

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

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