Benchmark: string.replace vs setUTCFullYear

HTML Preparation code:

<!--your preparation HTML code goes here-->

AخA
 
<!--your preparation HTML code goes here-->

Script Preparation code:

const date = "2025-03-05";
const yearToReplaceWith = "2017";

 
const date = "2025-03-05";const yearToReplaceWith = "2017";

Tests:

replace

const year = date.substring(0, 4);
const newDate = date.replace(year, yearToReplaceWith);

 
const year = date.substring(0, 4);const newDate = date.replace(year, yearToReplaceWith);

setUTCFullYear
const dateDate = new Date(date); dateDate.setUTCFullYear(yearToReplaceWith); const newDate = dateDate.toISOString().substring(0, 10);
const dateDate = new Date(date);
dateDate.setUTCFullYear(yearToReplaceWith);
const newDate = dateDate.toISOString().substring(0, 10);

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Experimental features:

Memory measurements supported only in Chrome.
For precise memory measurements Chrome must be launched with --enable-precise-memory-info flag.
More information: Monitoring JavaScript Memory

Test case name	Result
replace
setUTCFullYear

string.replace vs setUTCFullYear (version: 1)

Comparing performance of: replace vs setUTCFullYear

Created: 25 days ago by: Guest

Jump to the latest result

replace

setUTCFullYear

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

No previous run results