From: Yao Qi <yao@codesourcery.com>
To: "Agovic, Sanimir" <sanimir.agovic@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: ping: [PATCH 0/4 V3] GDB Performance testing
Date: Thu, 24 Oct 2013 14:13:00 -0000 [thread overview]
Message-ID: <52692A99.3080404@codesourcery.com> (raw)
In-Reply-To: <0377C58828D86C4588AEEC42FC3B85A71769EA52@IRSMSX105.ger.corp.intel.com>
On 10/24/2013 04:49 PM, Agovic, Sanimir wrote:
> + def measure(self, func, id):
> + """Measure the operations done by func with a collection of measurements."""
> + for m in self.measurements:
> + m.start(id)
> +
> + # Enable GC, force GC and disable GC before running test in order to reduce
> + # the interference from GC.
> + gc.enable()
> + gc.collect()
> + gc.disable()
> +
> + func()
> +
> + gc.enable()
> I`d rather exclude gc cycles completely from the measurements or include gc collection
> _after_ you run your perf test. Otherwise the results will depend on the order the perf
> tests are run.
Right, we should disable gc before measurements are started and enable
gc again when measurements are stopped. I'll update the patch.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-10-24 14:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 7:10 Yao Qi
2013-10-16 7:10 ` [PATCH 2/4] Perf test framework Yao Qi
2013-10-16 9:05 ` Yao Qi
2013-10-24 14:20 ` Yao Qi
2013-10-25 6:33 ` Doug Evans
2013-10-25 6:32 ` Doug Evans
2013-10-25 8:57 ` Yao Qi
2013-10-16 7:10 ` [PATCH 1/4] New make target 'check-perf' and new dir gdb.perf Yao Qi
2013-10-25 3:04 ` Doug Evans
2013-10-25 17:34 ` Pedro Alves
2013-10-16 7:10 ` [PATCH 4/4] Test on solib load and unload Yao Qi
2013-10-25 7:17 ` Doug Evans
2013-10-16 7:10 ` [PATCH 3/4] Mention perf test in testsuite/README Yao Qi
2013-10-25 6:43 ` Doug Evans
2013-10-24 2:44 ` ping: [PATCH 0/4 V3] GDB Performance testing Yao Qi
2013-10-24 8:50 ` Agovic, Sanimir
2013-10-24 14:13 ` Yao Qi [this message]
2013-10-25 2:59 ` 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=52692A99.3080404@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=sanimir.agovic@intel.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