Benchmark: Date.now() vs new Date().getTime()

Script Preparation code:

var timestamp = null;

Tests:

Date.now()
timestamp = Date.now();
new Date().getTime();
timestamp = new Date().getTime();

Historical Performance Data aggregated from 253 community runs

Desktop Results:

Chrome 190 runs

Date.now()

6.1M/s

new Date().getTime();

5.5M/s

Fastest: Date.now() (1.1x faster)

View exact numbers

✓ Date.now(): 6,084,433 ops/sec
• new Date().getTime();: 5,463,227 ops/sec

Firefox 30 runs

Date.now()

14.7M/s

new Date().getTime();

9.9M/s

Fastest: Date.now() (1.5x faster)

View exact numbers

✓ Date.now(): 14,682,636 ops/sec
• new Date().getTime();: 9,855,164 ops/sec

Safari 14 runs

Date.now()

10.6M/s

new Date().getTime();

10.3M/s

View exact numbers

✓ Date.now(): 10,595,820 ops/sec
• new Date().getTime();: 10,330,816 ops/sec

Other 7 runs

new Date().getTime();

2.1M/s

Date.now()

1.6M/s

Fastest: new Date().getTime(); (1.3x faster)

View exact numbers

✓ new Date().getTime();: 2,056,830 ops/sec
• Date.now(): 1,632,024 ops/sec

Mobile Results:

Chrome 7 runs

Date.now()

1.5M/s

new Date().getTime();

1.1M/s

Fastest: Date.now() (1.4x faster)

View exact numbers

✓ Date.now(): 1,463,449 ops/sec
• new Date().getTime();: 1,079,564 ops/sec

Safari 5 runs

Date.now()

24.5M/s

new Date().getTime();

18.4M/s

Fastest: Date.now() (1.3x faster)

View exact numbers

✓ Date.now(): 24,500,272 ops/sec
• new Date().getTime();: 18,391,706 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
Date.now()
new Date().getTime();

Fastest: N/A

Slowest: N/A

Latest run results:

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

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/OS: Chrome 142 on Mac OS X 10.15.7

View result in a separate tab

Date.now()

11.9M/s

new Date().getTime();

10.0M/s

View exact numbers

Test name	Executions per second
✓ Date.now()	11,865,902 Ops/sec
new Date().getTime();	9,972,737 Ops/sec

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

LLMs can make mistakes. Check important info.

**Overview**

The provided JSON represents a JavaScript benchmarking test case for measuring the performance difference between `Date.now()` and `new Date().getTime()`. This test is designed to evaluate the speed of these two functions in different browsers.

**What's being tested?**

Two functions are compared:

1. `Date.now()`: Returns the number of milliseconds since the Unix epoch (January 1, 1970) as a 32-bit integer.
2. `new Date().getTime()`: Returns the number of milliseconds since the Unix epoch (January 1, 1970) as a 64-bit integer.

**Options being compared**

The test case is comparing the performance of these two functions in different browsers.

Pros and Cons:

* `Date.now()`:
	+ Pros: Generally faster and more concise than `new Date().getTime()`.
	+ Cons: Returns an integer value, which may not be suitable for all use cases.
* `new Date().getTime()`:
	+ Pros: Returns a floating-point number with higher precision, making it suitable for applications requiring high accuracy.
	+ Cons: Generally slower and less concise than `Date.now()`.

**Other considerations**

The choice between `Date.now()` and `new Date().getTime()` depends on the specific use case:

* Use `Date.now()` when:
	+ You need to measure time intervals with a small margin of error (e.g., milliseconds).
	+ Code readability is more important than brevity.
* Use `new Date().getTime()` when:
	+ You require high precision in your timing measurements.
	+ You're working with legacy code or need to maintain compatibility.

**Library and special JS feature**

There are no libraries or special JavaScript features mentioned in the benchmarking test case. It solely focuses on comparing two native functions within JavaScript.

**Other alternatives**

If you want to measure the performance of other date-related functions or compare them with non-native JavaScript functions, you might consider using alternative benchmarks or libraries, such as:

* `Date.now()` vs `performance.now()`: A comparison between the two methods for measuring elapsed time.
* `new Date().getTime()` vs `Date.parse()`: An evaluation of the performance differences between these two functions for parsing dates.

Keep in mind that each test case requires careful consideration of the specific requirements and constraints of your application.

Date.now() vs new Date().getTime() (version: 0)

Comparing performance of: `Date.now() vs new Date().getTime();`

Created: 7 years ago by: Guest

Go to the latest result

Date.now()

new Date().getTime();

Historical Performance Data aggregated from 253 community runs

Desktop Results:

Chrome 190 runs

Firefox 30 runs

Safari 14 runs

Other 7 runs

Mobile Results:

Chrome 7 runs

Safari 5 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

Date.now() vs new Date().getTime() (version: 0)

Comparing performance of: Date.now() vs new Date().getTime();

Created: 7 years ago by: Guest

Go to the latest result

Date.now()

new Date().getTime();

Historical Performance Data aggregated from 253 community runs

Desktop Results:

Chrome 190 runs

Firefox 30 runs

Safari 14 runs

Other 7 runs

Mobile Results:

Chrome 7 runs

Safari 5 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.2:3b, generated one year ago):

Related benchmarks

Comparing performance of: `Date.now() vs new Date().getTime();`