Number.toLocaleString vs Intl.NumberFormat single instance 2 (version: 1)

Comparing performance of: Intl.NumberFormat vs Number.toLocaleString

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

Historical Performance Data aggregated from 6 community runs

Desktop Results:
Chrome 6 runs
Number.toLocaleString
10.0M/s
Intl.NumberFormat
8.1M/s

Fastest: Number.toLocaleString (1.2x faster)

View exact numbers
  • ✓ Number.toLocaleString: 10,025,536 ops/sec
  • • Intl.NumberFormat: 8,064,648 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
    Intl.NumberFormat
    Number.toLocaleString

    Fastest: N/A

    Slowest: N/A

Latest run results:
Run details: (Test run date: 4 months ago)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36 Edg/146.0.0.0
Chrome 146 on Windows
View result in a separate tab
Intl.NumberFormat
4.5M/s
Number.toLocaleString
151K/s
View exact numbers
Test name Executions per second
✓ Intl.NumberFormat 4,450,092 Ops/sec
Number.toLocaleString 150,675 Ops/sec

Related benchmarks