All committers have signed the CLA.

Beside this approach with tablewriter, we can also do some manual alignment with fmt.Sprintf and fixed string size to make it better. But that's a little more inconvenient. What do you think?

cool, maybe it is better to provide an output format flag, like table or origin raw message? so we can further support JSON, etc.

Another thing maybe we already used some scripts to parse the output results in our CI, so here we need to ensure the compatibility.

maybe we can also support this in https://github.com/pingcap/go-ycsb

@sillydong can you have a try later?

Seems like they are similar tools. If this approach has no problem, I will make it more formal and update this PR.
After we merge this PR I can do it again in go-ycsb.

cool, maybe it is better to provide an output format flag, like table or origin raw message? so we can further support JSON, etc.

I will try adding a flag output to control the output style, available values may be table,plaintext,json, the default will be table for human read. Is this OK?

Another thing maybe we already used some scripts to parse the output results in our CI, so here we need to ensure the compatibility.

Could you share more detail about the CI? I didn't find any thing for that, only a test case in hist_test.go. Is there anything more?

@sillydong

I will try adding a flag output to control the output style, available values may be table,plaintext,json, the default will be table for human read. Is this OK?

Fine, but IMO I prefer plain instead of plaintext :-)

For CI, means PingCAP's internal CI or bench system, has not been public.

cool, maybe it is better to provide an output format flag, like table or origin raw message? so we can further support JSON, etc.

I will try adding a flag output to control the output style, available values may be table,plaintext,json, the default will be table for human read. Is this OK?

Another thing maybe we already used some scripts to parse the output results in our CI, so here we need to ensure the compatibility.

Could you share more detail about the CI? I didn't find any thing for that, only a test case in hist_test.go. Is there anything more?

Inside PingCap, we've scripts to interpret the go-tpc result based on the current output format, please make the current format as the default for compatibility.

OK, the value would be plain,table,json, and default is plain.

For CI part, you may add cases for new formats after this.

any update? @sillydong

not yet, will update tonight

command help info is like this

here are some snapshots for output

plain

table

json

updated the go.mod

thanks @sillydong

can you do the same thing for go-ycsb?

working on learning the detail of go-ycsb, may take some time