Benchmark: Date resolver approaches

HTML Preparation code:

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

Script Preparation code:

const count = new Array(1000000);
const epoch = new Date(0);

const dateArray = count.map((i) => new Date(i));
const numberArray = count.map((i) => new Date(i).getTime());
const stringArray = count.map((i) => new Date(i).toISOString());

Tests:

Number converter
function dateResolver( value ) { return Number(value ?? 0) || new Date(value).getTime(); } let date; dateArray.forEach((value) => { date = dateResolver(value); }); numberArray.forEach((value) => { date = dateResolver(value); }); stringArray.forEach((value) => { date = dateResolver(value); });
Cascading ternary
function dateResolver( value ) { return value === undefined ? 0 : Number.isInteger(value) ? value : value instanceof Date ? value.getTime() : new Date(value).getTime(); } let date; dateArray.forEach((value) => { date = dateResolver(value); }); numberArray.forEach((value) => { date = dateResolver(value); }); stringArray.forEach((value) => { date = dateResolver(value); });

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Number converter
Cascading ternary

Fastest: N/A

Slowest: N/A

Latest run results:

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

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/26.1 Safari/605.1.15

Browser/OS: Safari 26 on Mac OS X 10.15.7

View result in a separate tab

Test name	Executions per second
Number converter	28.9 Ops/sec
Cascading ternary	28.6 Ops/sec

Related benchmarks:

Date resolver approaches (version: 1)

Comparing performance of: Number converter vs Cascading ternary

Created: 5 months ago by: Guest

Jump to the latest result

Number converter

Cascading ternary

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A