GitXplorerGitXplorer
M

jsFPerf

public
1 stars
3 forks
1 issues

Commits

List of commits on branch master.
Unverified
5d6c01831d5c76a0bc6fd276aa0eb71ad1424ce7

add mudash to mapFilterReduce

MMrRacoon committed 8 years ago
Unverified
992eaba96fd876746da4191cff8feb63ff1471d4

add lodash flowRight to mapFilterReduce

MMrRacoon committed 8 years ago
Unverified
46fdeec27b9a8a86513b8898a2e1fa3c1ebc38e1

add mapFilterReduce

MMrRacoon committed 8 years ago
Unverified
787d432dd37cdeb02d17cfeaa1607ae4231181db

add a composition benchmark

MMrRacoon committed 8 years ago
Unverified
a69245f37e7579160713de4da4c5fb348b05522b

moved to deep/wide sample types

MMrRacoon committed 8 years ago
Unverified
41ea2cb68d5e57e1f75673c3936c17a6bb8d27d5

Merge pull request #1 from jakegny/master

MMrRacoon committed 8 years ago

README

The README file for this repository.

jsFPerf

Build Status

To see the latest results, check the travis build.

Lots of talk about which immutable solution is faster and for what.

I made this repository because I was curious what the stats would be.

Installation

npm i -g jsfperf

Usage

By default, jsfperf will run all of the available tests with small sample sizes.

if You want to alter the size of the samples, you can choose between empty, singleton, deep, wide.

If you only want to run a subset of the tests, you can append their names to the command.

# run all tests with small samples
jsfperf

# run the find benchmark with wide samples
jsfperf -w find

# run the find and assocPath benchmarks with empty samples
jsfperf --empty find assocPath

# run all tests with deep samples
jsfperf --deep