GitXplorerGitXplorer
s

Perftests.jl

public
2 stars
3 forks
1 issues

Commits

List of commits on branch master.
Unverified
3967ba588ea224c088fe6a7d08c8b4d17dc51144

Add in sparse getindex_skinny tests

sstaticfloat committed 9 years ago
Unverified
87c29fff3e9e85331461458fa66fb3ff9369d0ba

Prettier printing, show elapsed time of each group

sstaticfloat committed 9 years ago
Unverified
c50e7da69a75ebb8054c30bd078eb246d1e7f63b

We don't need those poser modules anyway

sstaticfloat committed 9 years ago
Unverified
7f89a6e5f8a7c61243350da6c343a8badb687e10

Put benchmarks in their own modules

sstaticfloat committed 9 years ago
Unverified
a8d48b6cf4efd86fb81ce0d956fb90d491cf7621

A little more documentation

sstaticfloat committed 9 years ago
Unverified
4e4b91865ae3b3b866bff379a4abfcc007ec0803

Aha, that's how you do it

sstaticfloat committed 9 years ago

README

The README file for this repository.

Perftests

A redo of the main Julia test/perf directory. Retooled to use Benchmarks.jl, this repository will spit out a bunch of .csv files into the test/results-$COMMIT directory (Where $COMMIT is the commit hash of the version of Julia you are running) and display small summary statistics as it does so.

To run a specific group of tests, use run_perf_groups(). For example, to run and output the .csv files for the kernel and simd performance tests, one would write:

using Perftests
run_perf_groups(["kernel", "simd"])

Test organization

Tests are organized foremost by group, then name, then variant. Not all tests are required to have variants, but they fit into a natural hierarchy when running the same test across multiple element types, for example. The resultant .csv files are named $group-$name-$variant.csv, for ease of access.

Test environment

Information about the test environment (the commit hash of this repository used to create the results, the word size of the running machine, the number of CPU cores, etc...) is saved in the env.csv file put into the results-$COMMIT directory when testing.