SASADA Koichi ko1@atdot.net wrote:
(2014/02/28 16:44), normalperson@yhbt.net wrote:
It is easier to read output when columns are aligned properly.
I have an 80 column terminal, that's HUGE! Use it :D
Sorry, I can't read .gz file because of my environment.
unzipped versions:
before: http://80x24.org/bmlog-20140126-003136.7320.txt
after: http://80x24.org/bmlog-20140228-071544.1805.txt
What happen when many executables are specified (over 80 chars)?
This the timing lines after the text source is just aligned to the
longest line, so it looks like this:
ruby 2.2.0dev (2014-02-28 trunk 45211) [x86_64-linux] 0.071003417
built-ruby 0.0817603
Execution time summary header isn't changed, but the times themselves
look much better:
Execution time (sec)
name ruby 2.2.0dev (2014-02-28 trunk 45211) [x86_64-linux] built-ruby
app_answer 0.071 0.082
app_aobench 84.672 84.014
app_erb 1.511 1.524
I didn't check the speedup ratio header, but maybe the "name\tbuilt-ruby"
looks a little odd. I can fix that. The first line
("compare with the result of") is unchanged (and too long, but I don't
read that).
Speedup ratio: compare with the result of `ruby 2.2.0dev (2014-02-28 trunk 45211) [x86_64-linux]' (greater is better)
name built-ruby
app_answer 0.868
app_aobench 1.008
app_erb 0.992