# benchee_csv [![Hex Version](]( [![docs](]( [![Build Status](]( [![Coverage Status](](

Formatter for [benchee]( to turn the statistics output into a CSV file. This can then be used in the Spreadsheet tool of your choice to generate graphs to your liking.

These might then look like this one (quickly generated with LibreOffice from the output of the sample):

![sample graphs](

## Installation

Add benchee_csv to your list of dependencies in `mix.exs`:

def deps do
  [{:benchee_csv, "~> 0.7", only: :dev}]

Afterwards, run `mix deps.get` to install it.

## Usage

Simply configure `Benchee.Formatters.CSV` as one of the formatters for `` along with the file path you want the output to go (otherwise defaults to "benchmark_output.csv"):

list = Enum.to_list(1..10_000)
map_fun = fn i -> [i, i * i] end
    "flat_map" => fn -> Enum.flat_map(list, map_fun) end,
    "map.flatten" => fn -> list |> |> List.flatten() end
  formatters: [
    {Benchee.Formatters.CSV, file: "my.csv"},

The sample defines both the standard console formatter and the CSV formatter, if you don't care about the console output you can just delet that line.

You can also use the more verbose and versatile API of Benchee. When it comes to formatting just use `Benchee.Formatters.CSV.format/2` and then write it to a file (taking into account the new input structure). Check out the [samples directory]( for the verbose samples to see how it's done.

## Contributing

Contributions to benchee_csv are very welcome! Bug reports, documentation, spelling corrections, whole features, feature ideas, bugfixes, new plugins, fancy graphics... all of those (and probably more) are much appreciated contributions!

Please respect the [Code of Conduct](//

You can get started with a look at the [open issues](

A couple of (hopefully) helpful points:

* Feel free to ask for help and guidance on an issue/PR ("How can I implement this?", "How could I test this?", ...)
* Feel free to open early/not yet complete pull requests to get some early feedback
* When in doubt if something is a good idea open an issue first to discuss it
* In case I don't respond feel free to bump the issue/PR or ping me on other places

## Development

* `mix deps.get` to install dependencies
* `mix test` to run tests
* `mix credo` or `mix credo --strict` to find code style problems (not too strict with the 80 width limit for sample output in the docs)