From: Yao Qi <yao@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] rearrange struct value to save memory
Date: Tue, 14 Jan 2014 13:50:00 -0000 [thread overview]
Message-ID: <52D54032.3020406@codesourcery.com> (raw)
In-Reply-To: <87sisr1wgu.fsf@fleche.redhat.com>
On 01/14/2014 04:02 AM, Tom Tromey wrote:
> I tried perf-check out on another branch today. I didn't see a canned
> way to summarize the results, so I wrote the appended. You'll need a
> newish version of prettytable if you don't want the colorizing to mess
> up the table.
>
> This is still pretty dumb... I didn't try to deal with graphing or
> anything cool like that.
Yeah, we don't have scripts of this kind to compare the perf results,
but I think we need some.
At present, I am running perf tests continuously, and feed the result
to codespeed, in which the performance is shown as some diagrams. I
open them in web browser every day, to see if there are any perf
regressions. codespeed doesn't meet our needs perfectly, so I am
only running it in house and don't propose using it for GDB.
Performance data collection has been done, but perf data record
and comparison is still missing. I've had some thoughts, but
incomplete. I'll assemble them for a post to see how much we
can do here.
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-01-14 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 19:03 Tom Tromey
2014-01-10 3:32 ` Yao Qi
2014-01-10 17:12 ` Tom Tromey
2014-01-13 20:02 ` Tom Tromey
2014-01-14 13:50 ` Yao Qi [this message]
2014-01-16 21:54 ` Tom Tromey
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D54032.3020406@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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).