The containers-benchmark package

[Tags: bsd3, program]

This package evaluates performance of a containers package from multiple perspectives.

It measures time and memory allocation of methods specialised to several types. It can also measure the size and memory allocation of GHC compiled with the containers package.

The containers package used can be both system-installed or any darcs repository.

[Skip to ReadMe]


Change logCHANGES
Dependenciesbase (>=3 && <5), bytestring (>=0.9 && <1.0), containers (>=0.3 && <0.5), criterion (==0.5.*), random (==1.0.*) [details]
AuthorMilan Straka
Home page
UploadedTue Apr 19 13:20:20 UTC 2011 by MilanStraka
Downloads966 total (25 in last 30 days)
0 []
StatusDocs not available [build log]
All reported builds failed as of 2015-11-16 [all 3 reports]


Maintainers' corner

For package maintainers and hackage trustees

Readme for containers-benchmark-

This package consists of a thorough benchmark for a containers package.

Quick start
To benchmark the installed version of containers, just do

cd scripts
sh installed-containers none


The benchmark is executed using scripts in scripts directory. The main
executable is, which is given several arguments:
  name_of_the_benchmark      -- date is added to it
  containers_repo            -- repo with containers, write 'none' for
                             --   system containers library
  cabal_configure_opts       -- optional flags passed to cabal configure

The just calls other scripts: containers_repo cabal_configure_opts   -- builds the benchmark name_of_the_benchmark                      -- run built benchmark name_of_benchmark      -- collect all results in one .csv file

Other scripts: < name_of_csv              -- formats the csv file for viewing base_csv diff_csv          -- generate csv with comparison of two tests base_csv diff_csv          -- formats the result of for viewing containers_repo ghc_repo result_csv
    -- Compiles the GHC repo with given containers and store results
    -- the size of GHC and the memory allocation results of performance tests
    -- are stored. These tests were once a regression, so we monitor them.
    -- The GHC repo must be already booted and configured.

Which implementation to benchmark

The benchmark can use system-installed containers package or any given repo.
Because the criterion package used for benchmarking is using containers
internally, we cannot safely expose the benchmarked implementation as
Data.Map and others. Therefore we benchmark Container.{Map,Set,IntMap,IntSet}.
The scripts/ and scripts/ scripts
chooses which implementation of containers is benchmarked.

Benchmark design

Various input data are provided by InputData/*

Various benchmark methods are provided by Benchmar/*

As the different combinations of input data and containers result in different
type signatures, we use CPP extension to put the input data and benchmark
methods into one source file and let GHC to type-check for each combination of
input data and container. This happens in Variants/*