Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/4] Perf test framework
Date: Fri, 01 Nov 2013 19:43:00 -0000	[thread overview]
Message-ID: <CADPb22T+Lff34a0aw0+EhZTse+MAEg5mXHJFiJUWgp211JeuTw@mail.gmail.com> (raw)
In-Reply-To: <1383291300-13917-3-git-send-email-yao@codesourcery.com>

On Fri, Nov 1, 2013 at 12:34 AM, Yao Qi <yao@codesourcery.com> wrote:
> This patch adds a basic framework to do performance testing for GDB.
> perftest.py is about the test case, testresult.py is about test
> results, and how are they saved.  reporter.py is about how results
> are reported (in what format).  measure.py is about measuring the
> execution of tests by a collection of measurements.
>
> In V4:
>
>  - Rename MeasurementCPUTime to MeasurementCpuTime,
>  - Add 'pass' in empty method,
>  - Simplify string comparison in perftest.exp.
>  - Rename GDB_PERFORMANCE to GDB_PERFTEST_MODE and rename
>    GDB_PERFORMANCE_TIMEOUT to GDB_PERFTEST_TIMEOUT.
>
> In V3, there are some changes,
>
>  - Add wall time measurement, cpu time measurement and vmsize
>    measurement.
>  - Rename SingleStatisticTestCase to TestCaseWithBasicMeasurements,
>    which measures cpu time, wall time, and memory (vmsize).
>  - GDB_PERFORMANCE=run|compile|both to control the mode of perf
>    testing.
>  - New GDB_PERFORMANCE_TIMEOUT to specify the timeout.
>  - Split proc prepare to proc compile and startup.
>  - Disable GC while doing measurements.
>
> In V2, there are several changes to address Doug and Sanimir's
> comments.
>
>  - Add copyright header and docstring in perftest/__init__.py
>  - Remove config.py.
>  - Fix docstring format.
>  - Rename classes "SingleVariable" to "SingleStatistic".
>  - Don't extend gdb.Function in class TestCase.  Add a new method run
>    to run the test case so that we can pass parameters to test.
>  - Allow to customize whether to warm up and to append test log.
>  - Move time measurement into test harness.  Add a new class
>    Measurement for a specific measurement and a new class Measure to
>    measure them for a given test case.
>  - A new class ResultFactory to create instances of TestResult.
>  - New file lib/perftest.exp, which is to do some preparations and
>    cleanups to simplify each *.exp file.
>  - Skip compilation step if GDB_PERFORMANCE_SKIP_COMPILE is set.
>
> gdb/testsuite/
>
>         * lib/perftest.exp: New.
>         * gdb.perf/lib/perftest/__init__.py: New.
>         * gdb.perf/lib/perftest/measure.py: New.
>         * gdb.perf/lib/perftest/perftest.py: New.
>         * gdb.perf/lib/perftest/reporter.py: New.
>         * gdb.perf/lib/perftest/testresult.py: New.

Ok by me.
[Might want to give it a day or two to see if anyone else has any
final comments.]

Thanks for the perseverance!


  reply	other threads:[~2013-11-01 19:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01  7:36 [PATCH 0/4 V4] GDB Performance testing Yao Qi
2013-11-01  7:36 ` [PATCH 1/4] New make target 'check-perf' and new dir gdb.perf Yao Qi
2013-11-01  7:36 ` [PATCH 3/4] Mention perf test in testsuite/README Yao Qi
2013-11-01  7:36 ` [PATCH 2/4] Perf test framework Yao Qi
2013-11-01 19:43   ` Doug Evans [this message]
2013-11-01 20:46   ` Tom Tromey
2013-11-02  2:42     ` Yao Qi
2013-11-04 16:27       ` Tom Tromey
2013-11-06  5:30         ` Yao Qi
2013-11-01  7:36 ` [PATCH 4/4] Test on solib load and unload Yao Qi
2013-11-01 20:35   ` Tom Tromey
2013-11-02  2:50     ` Yao Qi
2013-11-04 17:37       ` Tom Tromey
2013-11-06  6:42 ` [PATCH 0/4 V4] GDB Performance testing Yao Qi
  -- strict thread matches above, loose matches on Subject: below --
2013-10-16  7:10 [PATCH 0/4 V3] " 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

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=CADPb22T+Lff34a0aw0+EhZTse+MAEg5mXHJFiJUWgp211JeuTw@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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