Benchmark name | When Created |
---|---|
Ramda vs. Lodash vs. Native array methods | 10 months ago |
Ramda vs. Lodash vs Native 2
Compares performance on the same task using Lodash vs two styles of Ramda vs two styles of "native" Javascript. In all cases the task is pulling "counter" property from each item in an array, filtering out odd items, squaring them, then returning those squared values that have less than two digits. |
10 months ago |
Ramda vs. Lodash vs Native
Compares performance on the same task using Lodash vs two styles of Ramda vs two styles of "native" Javascript. In all cases the task is pulling "counter" property from each item in an array, filtering out odd items, squaring them, then returning those squared values that have less than two digits. |
10 months ago |
One-pass vs native array methods | 10 months ago |
uderscorejs (1.13.6) vs jQuery (3.7.1) -- each | 10 months ago |
uderscore each vs jQuery each | 10 months ago |
RegEx.test vs. String.includes vs. String.startsWith | 10 months ago |
Object vs Class performance
Object vs Class performance |
10 months ago |
cached getComputedStyle vs. getBoundingClientRect 442 | 10 months ago |
Array initialization: preallocate vs push (Objects) | 10 months ago |
Symbol vs string vs string bracket vs indirect string | 10 months ago |
Create and append/remove versus display:block/display:none (improved) (without-recreating) (without-x-times)
By writing javascript web applications It is often common the need to show or hide elements like a div according to the user actions. Is it better to do this by creating and appending the node when it is needed or to create the node on the application start and then just display or hide it? This benchmark is a performance test of this particular use case. In this version, the createAppendDiv was isolated from operations that can be done once, so the test executes just the operations that are really essencial for the test case. |
10 months ago |
Create and append/remove versus display:block/display:none (improved) (without-recreating)
By writing javascript web applications It is often common the need to show or hide elements like a div according to the user actions. Is it better to do this by creating and appending the node when it is needed or to create the node on the application start and then just display or hide it? This benchmark is a performance test of this particular use case. In this version, the createAppendDiv was isolated from operations that can be done once, so the test executes just the operations that are really essencial for the test case. |
10 months ago |
Replace regex x replaceAll
Testing if replacing using Regex is faster |
10 months ago |
Object set vs new spread when reducing over results
Compare the new ES6 spread operator with the traditional concat() method and push |
10 months ago |
Array push vs spread when reducing over results
Compare the new ES6 spread operator with the traditional concat() method and push |
10 months ago |
for vs do while 2 | 10 months ago |
for i inside or outside var 3 | 10 months ago |
getElementsByClassName, For i, For of, For each, Some, Every, Map 2
getElementsByClassName, For i, For of, For each, Some, Every, Map |
10 months ago |
getElementById vs querySelector, with ten elements | 10 months ago |
getElementById vs querySelector, with two elements | 10 months ago |
Function call vs Object
Compare Function calls vs Object |
10 months ago |
JSON Stringify Speed Test - Large Payloads
This benchmark tests whether the speed or JSON.stringify changes with object size |
10 months ago |
JSON Stringify Speed Test 13 -
This benchmark tests whether the speed or JSON.stringify changes with object size |
10 months ago |
JSON Stringify Speed Test 13
This benchmark tests whether the speed or JSON.stringify changes with object size |
10 months ago |