Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export to JSON #42

Closed
stevepentland opened this issue Mar 18, 2018 · 4 comments
Closed

Export to JSON #42

stevepentland opened this issue Mar 18, 2018 · 4 comments

Comments

@stevepentland
Copy link
Contributor

This covers exporting results to JSON as outlined in #38 and extends on the work done on #41.

The same format of --export-xxx should be used (in this case --export-json) with a filename parameter following. It should exist peacefully with simultaneous usage of --export-csv and multiple instances of both.

@sharkdp
Copy link
Owner

sharkdp commented Mar 18, 2018

Something I would like to see for the JSON export (probably not for the CSV export) is a list of all measured times. These could be listed in addition to the statistical properties. What do you think?

(this is something we can also add at a later stage, let's focus on #41 first)

@stevepentland
Copy link
Contributor Author

Sure, that can also be added on once the generic export mechanisms are hammered out. Since we're using serde, there may actually be some facility to ignore a field or set of fields for a given export type.

@sharkdp
Copy link
Owner

sharkdp commented Mar 21, 2018

Closed via #45 and #48

@sharkdp sharkdp closed this as completed Mar 21, 2018
@sharkdp
Copy link
Owner

sharkdp commented Mar 21, 2018

A small Python script that can be used to plot benchmark results that have been exported to JSON:

https://gist.github.com/sharkdp/e1712590690aa95df65f5a73751d33a9

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants