Benchmark: Number constructor vs unary plus vs parseInt

Number constructor vs unary plus vs parseInt (version: 0)

Comparing performance of: Number (with string integer) vs Unary + (with string integer) vs parseInt (with string integer) vs Number (with string float) vs Unary + (with string float) vs parseInt (with string float) vs Number (with integer) vs Unary + (with integer) vs parseInt (with integer) vs Number (with float) vs Unary + (with float) vs parseInt (with float) vs Number (with NaN) vs Unary + (with NaN) vs parseInt (with NaN)

Created: 3 years ago by: Guest

Jump to the latest result

Tests:

Number (with string integer)
var numberStrInt = Number(Math.floor(1000 * Math.random()).toString());
Unary + (with string integer)
var unaryStrInt = +Math.floor(1000 * Math.random()).toString();
parseInt (with string integer)
var parseStrInt = parseInt(Math.floor(1000 * Math.random()).toString(), 10);
Number (with string float)
var numberStrFloat = Number((1000 * Math.random()).toString());
Unary + (with string float)
var unaryStrFloat = +(1000 * Math.random()).toString();
parseInt (with string float)
var parseStrFloat = parseInt((1000 * Math.random()).toString(), 10);
Number (with integer)
var numberNumInt = Number(Math.floor(1000 * Math.random()));
Unary + (with integer)
var unaryNumInt = +Math.floor(1000 * Math.random());
parseInt (with integer)
var parseNumInt = parseInt(Math.floor(1000 * Math.random()), 10);
Number (with float)
var numberNumFloat = Number(1000 * Math.random());
Unary + (with float)
var unaryNumFloat = +(1000 * Math.random());
parseInt (with float)
var parseNumFloat = parseInt((1000 * Math.random()), 10);
Number (with NaN)
var numberNaN = Number("hello");
Unary + (with NaN)
var unaryNaN = +("hello");
parseInt (with NaN)
var parseNaN = parseInt("hello", 10);

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
Number (with string integer)
Unary + (with string integer)
parseInt (with string integer)
Number (with string float)
Unary + (with string float)
parseInt (with string float)
Number (with integer)
Unary + (with integer)
parseInt (with integer)
Number (with float)
Unary + (with float)
parseInt (with float)
Number (with NaN)
Unary + (with NaN)
parseInt (with NaN)

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: 29 days ago)

User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36

Browser/OS: Chrome 131 on Linux

View result in a separate tab

Test name	Executions per second
Number (with string integer)	3664614.0 Ops/sec
Unary + (with string integer)	5145685.0 Ops/sec
parseInt (with string integer)	3642761.5 Ops/sec
Number (with string float)	2474587.5 Ops/sec
Unary + (with string float)	3126319.0 Ops/sec
parseInt (with string float)	2549427.0 Ops/sec
Number (with integer)	3973418.8 Ops/sec
Unary + (with integer)	5831906.5 Ops/sec
parseInt (with integer)	3754734.8 Ops/sec
Number (with float)	5604960.5 Ops/sec
Unary + (with float)	10376790.0 Ops/sec
parseInt (with float)	5385101.5 Ops/sec
Number (with NaN)	11171146.0 Ops/sec
Unary + (with NaN)	115805384.0 Ops/sec
parseInt (with NaN)	11301867.0 Ops/sec

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

LLMs can make mistakes. Check important info.

It seems like you're sharing a JSON-formatted text with an array of objects, each representing a test case from a web browser performance benchmarking experiment.

If I had to extract insights from this data, here are some observations:

1. **Browser Performance Consistency**: The Chrome 128 browser variant consistently performs well across various tests, suggesting its optimized architecture and performance features.
2. **Device Platform Variation**: Tests on Mac OS X platforms demonstrate slightly higher execution rates compared to other operating systems.
3. **Test Variability**: Different test cases (e.g., `parseInt`, `Unary +`, `Number`) exhibit varying performance characteristics, highlighting the importance of each specific use case in browser optimization.
4. **Execution Rate Fluctuations**: Small variations in execution per second occur between tests, potentially due to differences in input data or algorithmic implementation.

Would you like me to analyze anything else from this dataset?

Related benchmarks:

Number constructor vs unary plus vs parseInt (version: 0)

Created: 3 years ago by: Guest

Jump to the latest result

Number (with string integer)

Unary + (with string integer)

parseInt (with string integer)

Number (with string float)

Unary + (with string float)

parseInt (with string float)

Number (with integer)

Unary + (with integer)

parseInt (with integer)

Number (with float)

Unary + (with float)

parseInt (with float)

Number (with NaN)

Unary + (with NaN)

parseInt (with NaN)

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A

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