From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/4 V3] GDB Performance testing
Date: Wed, 16 Oct 2013 07:10:00 -0000 [thread overview]
Message-ID: <1381907353-30013-1-git-send-email-yao@codesourcery.com> (raw)
Hi,
Here is the V3 of GDB performance testing. The changes in V3 can be
found in each patch, and they address all review comments.
The basic usages of performance testing are unchanged,
$ make check-perf
$ make check-perf RUNTESTFLAGS="--target_board=native-gdbserver solib.exp"
$ make check-perf RUNTESTFLAGS="solib.exp SOLIB_COUNT=512"
We can skip compilation step like,
$ make check-perf RUNTESTFLAGS='solib.exp GDB_PERFORMANCE=run'
or only compile test cases,
$ make check-perf RUNTESTFLAGS='solib.exp GDB_PERFORMANCE=compile'
in default, GDB_PERFORMANCE=both.
If the perf test case takes much time, we can specify timeout by
GDB_PERFORMANCE_TIMEOUT=1000.
$ make check-perf RUNTESTFLAGS="--target_board=native-gdbserver GDB_PERFORMANCE_TIMEOUT=4000 solib.exp"
Looks the perf test framework is in shape, so I add the patch to
testsuite/README to describe perf test.
The output in testsuite/perftest.log is like this:
solib_load cpu_time 32 0.05
solib_load cpu_time 64 0.13
solib_load cpu_time 128 0.36
solib_load cpu_time 256 1.16
solib_load cpu_time 512 4.93
solib_load wall_time 32 0.0982959270477
solib_load wall_time 64 0.261036157608
solib_load wall_time 128 0.848724126816
solib_load wall_time 256 3.21620082855
solib_load wall_time 512 15.2153270245
solib_load vmsize 32 94632
solib_load vmsize 64 94652
solib_load vmsize 128 94696
solib_load vmsize 256 94780
solib_load vmsize 512 110664
solib_unload cpu_time 32 0.03
solib_unload cpu_time 64 0.08
solib_unload cpu_time 128 0.22
solib_unload cpu_time 256 0.74
solib_unload cpu_time 512 2.64
solib_unload wall_time 32 0.0625808238983
solib_unload wall_time 64 0.183571815491
solib_unload wall_time 128 0.655772924423
solib_unload wall_time 256 2.67978000641
solib_unload wall_time 512 12.8180861473
solib_unload vmsize 32 109648
solib_unload vmsize 64 109648
solib_unload vmsize 128 109648
solib_unload vmsize 256 109648
solib_unload vmsize 512 110440
*** BLURB HERE ***
Yao Qi (4):
New make target 'check-perf' and new dir gdb.perf
Perf test framework
Mention perf test in testsuite/README
Test on solib load and unload
gdb/Makefile.in | 8 +
gdb/testsuite/Makefile.in | 4 +
gdb/testsuite/README | 27 ++++
gdb/testsuite/configure | 3 +-
gdb/testsuite/configure.ac | 2 +-
gdb/testsuite/gdb.perf/Makefile.in | 15 ++
gdb/testsuite/gdb.perf/lib/perftest/__init__.py | 17 +++
gdb/testsuite/gdb.perf/lib/perftest/measure.py | 146 ++++++++++++++++++++
gdb/testsuite/gdb.perf/lib/perftest/perftest.py | 72 ++++++++++
gdb/testsuite/gdb.perf/lib/perftest/reporter.py | 64 +++++++++
gdb/testsuite/gdb.perf/lib/perftest/testresult.py | 57 ++++++++
gdb/testsuite/gdb.perf/solib.c | 78 +++++++++++
gdb/testsuite/gdb.perf/solib.exp | 78 +++++++++++
gdb/testsuite/gdb.perf/solib.py | 73 ++++++++++
gdb/testsuite/lib/gdb.exp | 16 +++
gdb/testsuite/lib/perftest.exp | 148 +++++++++++++++++++++
16 files changed, 806 insertions(+), 2 deletions(-)
create mode 100644 gdb/testsuite/gdb.perf/Makefile.in
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/__init__.py
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/measure.py
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/perftest.py
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/reporter.py
create mode 100644 gdb/testsuite/gdb.perf/lib/perftest/testresult.py
create mode 100644 gdb/testsuite/gdb.perf/solib.c
create mode 100644 gdb/testsuite/gdb.perf/solib.exp
create mode 100644 gdb/testsuite/gdb.perf/solib.py
create mode 100644 gdb/testsuite/lib/perftest.exp
--
1.7.7.6
next reply other threads:[~2013-10-16 7:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 7:10 Yao Qi [this message]
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 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 3/4] Mention perf test in testsuite/README Yao Qi
2013-10-25 6:43 ` Doug Evans
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-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
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=1381907353-30013-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.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