-
Notifications
You must be signed in to change notification settings - Fork 166
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
[suggestion] multiple output-formats #476
Comments
Good suggestion, not completely trivial. |
Here is the patch for parsing the input, however, the refactoring for the recursive output would require a major rewrite of various parts as it is reported in line with the code and not written after an experiment is completed. One issue is that errors and output is created as soon as it is available and no information is collected and then written afterwards.
|
I really welcome the "-O summaryFormat=json" - as it allows more correct/easier parsing and processing of IOR-outputs.
BUT - as I have a lot of "legacy" parsers - I can't easily switch over to 'json' only output.
So it would be practical - to have something like "-O summaryFormat=json,default" - and have BOTH generated.
Sounds 'whacky' at first - I know - but look at FIO - it actually does the SAME! - and the idea works quite well there.
YES - it's quite 'messy' to have first text, then json (or vice versa) - but if you request 'default,json' - you know what you want.
(maybe it should even honor the order - so 'default,json' - or 'json,default' )
I still do need the human-readable text - to be able to show it to someone else.
(you can't paste a json-output into a benchmark report)
But for analyzing a large ammount of runs - having JSON additionally - would be really nice.
The text was updated successfully, but these errors were encountered: