-
Notifications
You must be signed in to change notification settings - Fork 127
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
blocks-import-script: add --markdown flag and remove --csv-output flag #2985
base: master
Are you sure you want to change the base?
Conversation
|
print("\nbpsd = blocks per sec diff (+), tpsd = txs per sec diff, timed = time to process diff (-)") | ||
print("+ = more is better, - = less is better") | ||
if args.markdown: | ||
write_markdown_output(stats_df, df, args.baseline, args.contender) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to treat markdown in the same way as CSV?
Currently it's CSV (optional) + MD or standard output. I would make it CSV (optional) + MD (optional) + standard output.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
currently markdown is optional. If we don't pass --markdown
flag only tab spaced data is returned in standard output.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in latest commit I've made it more explicit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
csv is also optional.
I think standard output is good for stdout, but for file formats better save them separately (csv, md,..)
505a445
to
bb00e61
Compare
bb00e61
to
3a3eb26
Compare
In python : The brackets
|
my preference would broadly be that we cut down on the output formats to as few as possible - ie either csv or markdown - there's no point maintaining a bunch of formats that don't get used. |
I like |
whatever is minimally legible .. I'd even be fine with dumping the regular text output into triple-quotes or a table or a csv or any variation thereof. It doesn't greatly matter as long as it doesn't require multiple clicks to get to. The fewer the clicks and scrolling the better. In terms of importance, I think the "main" readme that lists all benchmarks in a big table is the most important one - this is where we can get a quick overview whether a particular commit slowed something down. Having to drill down into each folder takes ages. |
You can keep CSV and then just use a converter tool - one of many, like csv2md - and just convert it afterwards. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The markdown formatting code could use refactoring but it's good enough for now.
print("\nbpsd = blocks per sec diff (+), tpsd = txs per sec diff, timed = time to process diff (-)") | ||
print("+ = more is better, - = less is better") | ||
if args.markdown: | ||
write_markdown_output(stats_df, df, args.baseline, args.contender) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
csv is also optional.
I think standard output is good for stdout, but for file formats better save them separately (csv, md,..)
Summary
This PR adds
--markdown
support to blocks import script.This PR also removed
--csv-output
flag.This option can be used like this
The output is a nice markdown table :
blocks-import-benchmark.csv vs blocks-import-benchmark.csv
Summary
Legend
(+) = more is better, (-) = less is better