Benchmark: old range vs new range

Script Preparation code:

function rangefunction(number) {
  return Array.apply(null, { length: number }).map(eval.call, Number)
}

var rangevar = number => [...Array(number).keys()]

Tests:

old range
function range(number) { return Array.apply(null, { length: number }).map(eval.call, Number) } range(1000)
new range
const range = number => [...Array(number).keys()] range(1000)
old range - just use
rangefunction(1000)
new range - just use
rangevar(1000)
old range - just define
function range(number) { return Array.apply(null, { length: number }).map(eval.call, Number) }
new range - just define
const range = number => [...Array(number).keys()]

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
old range
new range
old range - just use
new range - just use
old range - just define
new range - just define

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: 7 years ago)

User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2871.0 Safari/537.36

Browser/OS: Chrome 55 on Mac OS X 10.12.1

View result in a separate tab

Test name	Executions per second
old range	7687.9 Ops/sec
new range	7960.5 Ops/sec
old range - just use	7784.8 Ops/sec
new range - just use	9304.3 Ops/sec
old range - just define	55451500.0 Ops/sec
new range - just define	54982600.0 Ops/sec

old range vs new range (version: 0)

Comparing performance of: old range vs new range vs old range - just use vs new range - just use vs old range - just define vs new range - just define

Created: 7 years ago by: Guest

Jump to the latest result

old range

new range

old range - just use

new range - just use

old range - just define

new range - just define

Suite status: <idle, ready to run>

Experimental features:

Fastest: N/A

Slowest: N/A