Number() vs parseFloat() (version: 4)

Comparing performance of: Number vs parseFloat vs String concat1 vs String concat2 vs -0 vs *1

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

Historical Performance Data aggregated from 13 community runs

Desktop Results:
Chrome 13 runs
-0
722.5M/s
*1
719.2M/s
Number
121.5M/s
String concat1
17.7M/s
parseFloat
15.4M/s
String concat2
7.6M/s

Fastest: -0 (94.8x faster)

View exact numbers
  • ✓ -0: 722,549,312 ops/sec
  • • *1: 719,224,192 ops/sec
  • • Number: 121,465,504 ops/sec
  • • String concat1: 17,734,402 ops/sec
  • • parseFloat: 15,380,018 ops/sec
  • • String concat2: 7,625,107 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
    Number
    parseFloat
    String concat1
    String concat2
    -0
    *1

    Fastest: N/A

    Slowest: N/A

Latest run results:
Run details: (Test run date: 6 months ago)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36 Edg/143.0.0.0
Chrome 143 on Windows
View result in a separate tab
-0
101.9M/s
Number
100.7M/s
String concat2
100.6M/s
*1
98.0M/s
String concat1
97.5M/s
parseFloat
10.1M/s
View exact numbers
Test name Executions per second
✓ -0 101,865,008 Ops/sec
Number 100,717,776 Ops/sec
String concat2 100,643,968 Ops/sec
*1 98,048,888 Ops/sec
String concat1 97,471,464 Ops/sec
parseFloat 10,124,873 Ops/sec

Related benchmarks