Run results for: toDateString() vs. getFullYear(), getMonth(), and getDate() equality check

Run details:

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36

Browser: Chrome 142

Operating system: Mac OS X 10.15.7

Device Platform: Desktop

Date tested: 8 months ago

Custom function using getFullYear(), getMonth(), and getDate() equality check

18.3M/s

toDateString() equality check

2.7M/s

View exact numbers

Test name	Executions per second
✓ Custom function using getFullYear(), getMonth(), and getDate() equality check	18,311,238 Ops/sec
toDateString() equality check	2,701,705 Ops/sec

HTML Preparation code:

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

Script Preparation code:

/*your preparation JavaScript code goes here
To execute async code during the script preparation, wrap it as function globalMeasureThatScriptPrepareFunction, example:*/
async function globalMeasureThatScriptPrepareFunction() {
    // This function is optional, feel free to remove it.
    // await someThing();
}

Tests:

Custom function using getFullYear(), getMonth(), and getDate() equality check
function isSameDate(dateA, dateB) { return ( dateA.getFullYear() === dateB.getFullYear() && dateA.getMonth() === dateB.getMonth() && dateA.getDate() === dateB.getDate() ); } let sampleDate1 = new Date() return isSameDate(sampleDate1,sampleDate1)
toDateString() equality check
let sampleDate2 = new Date() return sampleDate2.toDateString() === sampleDate2.toDateString()

Run results for: toDateString() vs. getFullYear(), getMonth(), and getDate() equality check

Compare how equality checks using toDateString() compares to a custom function that relies on getFullYear(), getMonth(), and getDate()

Custom function using getFullYear(), getMonth(), and getDate() equality check

toDateString() equality check