Benchmark: Float string optimization: parseFloat() vs regex

Tests:

parseFloat()
var string = parseFloat((3/2).toFixed(4)).toString();
regex
var string = (3/2).toFixed(4).replace(/\.?0*$/, '');

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
parseFloat()
regex

Fastest: N/A

Slowest: N/A

ⓘ Get performance results from real users on your website with Request Metrics.

Website Performance Monitoring by Request Metrics

Latest run results:

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

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36 OPR/107.0.0.0 (Edition std-1)

Browser/OS: Opera 107 on Windows

View result in a separate tab

Test name	Executions per second
parseFloat()	6294064.0 Ops/sec
regex	9332878.0 Ops/sec

Float string optimization: parseFloat() vs regex (version: 0)

To get a cleaned-up float number with a limited number of digits of precision, which is faster: parsefloat() or a regular expression?

Comparing performance of: parseFloat() vs regex

Created: 3 years ago by: Guest

Jump to the latest result

parseFloat()

regex

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A