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

ⓘ Get performance results from real users on your website with Request Metrics.

Website Performance Monitoring by Request Metrics

Latest run results:

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

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

Browser/OS: Firefox 97 on Linux

View result in a separate tab

Test name	Executions per second
Split on space	2078163.0 Ops/sec
Regex replace and trim	3826478.0 Ops/sec
Regex replace without global	6793900.0 Ops/sec

Regex vs split for Authorization Headers (version: 0)

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: 2 years ago by: Guest

Jump to the latest result

Split on space

Regex replace and trim

Regex replace without global

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A