Benchmark: RegExp unnecessary matches implications

Script Preparation code:

var matches = [
  'this_is_a_match',
  'another_match',
  'match_with_numbers_9',
  '100_200_300_400_500'
];

var no_matches = [
  'this_is_not_a-match',
  'another_no_match@',
  'no_match_with_numbers_9_*',
  '100_200_300_400_500_#'
];

Tests:

With unnecessary matches
var result_matches = matches.map((str) => /^[\w\d_]+$/.test(str)); var result_no_matches = no_matches.map((str) => /^[\w\d_]+$/.test(str));
Without unnecessary matches
var result_matches = matches.map((str) => /^\w+$/.test(str)); var result_no_matches = no_matches.map((str) => /^\w+$/.test(str));

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
With unnecessary matches
Without unnecessary matches

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: one year ago)

User agent: Mozilla/5.0 (iPhone; CPU iPhone OS 16_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/113.0.5672.69 Mobile/15E148 Safari/604.1

Browser/OS: Chrome Mobile iOS 113 on iOS 16.5

View result in a separate tab

Test name	Executions per second
With unnecessary matches	2526798.0 Ops/sec
Without unnecessary matches	3325580.0 Ops/sec

RegExp unnecessary matches implications (version: 7)

Check if having unnecessary matches in a regular expression has some performance implication

Comparing performance of: With unnecessary matches vs Without unnecessary matches

Created: one year ago by: Registered User

Jump to the latest result

With unnecessary matches

Without unnecessary matches

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A