Some Date getters/setters (version: 1)

Comparing performance of: getTime() vs getMinutes() vs getUTCMinutes vs setMinutes() vs getTimezoneOffset() vs toString()

Created: one year ago by: Guest
Go to the latest result
HTML Preparation code:
Script Preparation code:
Tests:

Historical Performance Data aggregated from 14 community runs

Desktop Results:
Chrome 14 runs
getTime()
94.0M/s
getUTCMinutes
29.0M/s
getMinutes()
71K/s
getTimezoneOffset()
64K/s
toString()
24K/s
setMinutes()
17K/s

Fastest: getTime() (5471.6x faster)

View exact numbers
  • ✓ getTime(): 93,959,648 ops/sec
  • • getUTCMinutes: 29,007,476 ops/sec
  • • getMinutes(): 71,363 ops/sec
  • • getTimezoneOffset(): 63,798 ops/sec
  • • toString(): 24,097 ops/sec
  • • setMinutes(): 17,172 ops/sec

Results show median performance across all community submissions. Run this benchmark yourself to verify on your device.

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results
  • Test case name Result
    getTime()
    getMinutes()
    getUTCMinutes
    setMinutes()
    getTimezoneOffset()
    toString()

    Fastest: N/A

    Slowest: N/A

Latest run results:
Run details: (Test run date: one year ago)
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36
Chrome 139 on Linux
View result in a separate tab
getTime()
91.3M/s
getUTCMinutes
26.6M/s
getMinutes()
63K/s
getTimezoneOffset()
29K/s
toString()
24K/s
setMinutes()
10K/s
View exact numbers
Test name Executions per second
✓ getTime() 91,285,304 Ops/sec
getUTCMinutes 26,598,262 Ops/sec
getMinutes() 62,764 Ops/sec
getTimezoneOffset() 29,172 Ops/sec
toString() 24,007 Ops/sec
setMinutes() 9,752 Ops/sec

Related benchmarks