From: Yao Qi <yao@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/3] change gdbserver to use hashtab: list->table
Date: Sun, 26 Jan 2014 01:48:00 -0000 [thread overview]
Message-ID: <52E468CF.3060008@codesourcery.com> (raw)
In-Reply-To: <52E3ADB8.60707@codesourcery.com>
On 01/25/2014 08:27 PM, Yao Qi wrote:
>> [In one perf experiment of attach/detach repeated 20 times on a
>> > program with 1000 threads, the time as measured by gprof went from
>> > 45sec to 5sec.]
>> >
>> > I created a testcase for our perf testsuite but the results there
>> > don't show the speed as impressively because it can only measure gdb
>> > not gdbserver. I may submit it separately anyway.
> Hi, Doug,
> Please do that. If gdbserver becomes faster, the improvements should
> be shown in the perf test result. I'd like to help on this.
>
The speedup isn't shown probably because there are too many RSP
communications between GDB and GDBserver, which is slow.
It is still good to include your test case into the gdb.perf testsuite.
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-01-26 1:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 1:12 Doug Evans
2014-01-25 12:29 ` Yao Qi
2014-01-26 1:48 ` Yao Qi [this message]
2014-01-26 23:01 ` Doug Evans
2014-01-29 5:45 ` Doug Evans
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=52E468CF.3060008@codesourcery.com \
--to=yao@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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