From: normalperson@yhbt.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:61148] [ruby-trunk - Feature #9577] [PATCH] benchmark/driver.rb: align columns in text output
Date: Fri, 28 Feb 2014 16:42:46 +0000 [thread overview]
Message-ID: <redmine.journal-45521.20140228164245.e8e9ca0fefdead40@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-9577.20140228074416@ruby-lang.org
Issue #9577 has been updated by Eric Wong.
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
----------------------------------------
Feature #9577: [PATCH] benchmark/driver.rb: align columns in text output
https://bugs.ruby-lang.org/issues/9577#change-45521
* Author: Eric Wong
* Status: Open
* Priority: Low
* Assignee: Eric Wong
* Category: misc
* Target version: current: 2.2.0
----------------------------------------
It is easier to read output when columns are aligned properly.
I have an 80 column terminal, that's HUGE! Use it :D
pulL: git://80x24.org/ruby.git bmdriver-align
patch: http://bogomips.org/ruby.git/patch?id=32eed05c80
samples
before: http://80x24.org/bmlog-20140126-003136.7320.gz
after: http://80x24.org/bmlog-20140228-071544.1805.gz
I'll commit soon unless this breaks some tools (or this makes life hard
for the 40-column people :P)
--
http://bugs.ruby-lang.org/
next prev parent reply other threads:[~2014-02-28 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-9577.20140228074416@ruby-lang.org>
2014-02-28 7:44 ` [ruby-core:61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output normalperson
2014-02-28 12:26 ` [ruby-core:61144] " SASADA Koichi
2014-02-28 16:38 ` [ruby-core:61146] " Eric Wong
2014-02-28 12:30 ` [ruby-core:61145] [ruby-trunk - Feature #9577] " ko1
2014-02-28 16:42 ` normalperson [this message]
2018-11-30 14:33 ` [ruby-core:90191] [Ruby trunk Feature#9577][Closed] " takashikkbn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-45521.20140228164245.e8e9ca0fefdead40@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).