Benchmark: Regex vs split for Authorization Headers

Script Preparation code:

var authHeader = 'Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyLCJkZnMiOiJhZGZzamxrO2FzZGZqbGs7c2RmYWtqbDthc2RmamtsIiwiaXNzIjoiaHR0cHM6Ly92ZXJ5LnZlcnkudmVyeS52ZXJ5LnZlcnkubG9uZy5leGFtcGxlLmNvbSJ9.RGmluP8NjlKuiow57PkkAZLUCwclllRBPURJU7Hajmo';

Tests:

Split on space
authHeader.split(' ')[1]
Regex replace and trim
authHeader.replace(/Bearer/g,'').trim()
Regex replace without global
authHeader.replace(/Bearer /,'')

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Split on space
Regex replace and trim
Regex replace without global

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 3 months ago)

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:151.0) Gecko/20100101 Firefox/151.0

Browser/OS: Firefox 151 on Linux

View result in a separate tab

Regex replace without global

22.2M/s

Regex replace and trim

10.9M/s

Split on space

10.1M/s

View exact numbers

Test name	Executions per second
✓ Regex replace without global	22,173,222 Ops/sec
Regex replace and trim	10,948,417 Ops/sec
Split on space	10,070,045 Ops/sec

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

LLMs can make mistakes. Check important info.

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

**Benchmark Definition**

The benchmark is designed to compare three different approaches for extracting an authorization header from a string:

1. **Regex vs split**: This approach uses the `split()` method to divide the string into two parts at each occurrence of a space character, and then takes the second part (index 1) as the extracted header.
2. **Regex replace and trim**: This approach uses a regular expression (`/Bearer/g`) to remove all occurrences of "Bearer " from the start of the string, followed by `trim()` to remove any leading or trailing whitespace.
3. **Regex replace without global**: This approach is similar to the second one, but it doesn't use the `/g` flag, which means the regular expression won't be applied globally across the entire string.

**Library and purpose**

The `split()` method is a built-in JavaScript method that splits a string into an array of substrings based on a specified separator. In this case, the separator is a space character (`' '`).

No additional libraries are required for these tests.

**Special JS feature or syntax**

None of the test cases use any special JavaScript features or syntax. They only rely on standard JavaScript methods and operators.

**Pros and cons of each approach**

Here's a brief summary of the pros and cons of each approach:

1. **Regex vs split**: This approach is simple and efficient, but it may not be as accurate if there are multiple spaces between the "Bearer" token.
2. **Regex replace and trim**: This approach is more robust than `split()` because it doesn't rely on a specific separator. However, it requires two separate operations (replace and trim), which might be slower due to function call overhead.
3. **Regex replace without global**: This approach is similar to the second one but without the `/g` flag. It's likely to be slightly faster than the second one because it doesn't need an additional pass across the entire string.

**Other alternatives**

Some alternative approaches could include:

* Using a dedicated library like `regex-authorization-header` (although this seems to be more of a specialized header parsing library, not specifically for benchmarking regex vs split)
* Implementing custom extraction logic using JavaScript's `String.prototype.indexOf()` and `slice()` methods
* Using other string manipulation libraries or frameworks that provide optimized regex matching or splitting functions.

Keep in mind that these alternatives might not offer significant performance improvements over the original three approaches.

Regex vs split for Authorization Headers (version: 0) Benchmark.js

Is it faster to get the meat from an Authorization header by splitting on the space? or using a regex replace and trim?

Comparing performance of: `Split on space vs Regex replace and trim vs Regex replace without global`

Created: 4 years ago by: Guest

Go to the latest result

Split on space

Regex replace and trim

Regex replace without global

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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

Regex vs split for Authorization Headers (version: 0) Benchmark.js

Is it faster to get the meat from an Authorization header by splitting on the space? or using a regex replace and trim?

Comparing performance of: Split on space vs Regex replace and trim vs Regex replace without global

Created: 4 years ago by: Guest

Go to the latest result

Split on space

Regex replace and trim

Regex replace without global

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

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

Related benchmarks

Comparing performance of: `Split on space vs Regex replace and trim vs Regex replace without global`