diff options
author | Alexander Larsson <alexl@redhat.com> | 2009-08-20 14:34:51 +0200 |
---|---|---|
committer | Alexander Larsson <alexl@redhat.com> | 2009-10-02 21:02:23 +0200 |
commit | b1f94af095bde6a9a695ce7b19425a62288ee0ee (patch) | |
tree | bda053f5777413a2dd2fef6fa9bf4dee1deb2d03 /tests/markups | |
parent | 07ad638adff596ccd4bc2ec003be692059210357 (diff) | |
download | glib-b1f94af095bde6a9a695ce7b19425a62288ee0ee.tar.gz |
Add performance tests for GObject primitives
These are basic performance test for a couple of basic gobject
primitives:
* construction of simple objects. Simple is a bare gobject derived
class with no properties, signals or interfaces.
* construction of complex objects. Complex is a gobject subclass
with construct properties, normal properties, signals, and
implements an interface.
* run-time type check of complex objects
* signal emissions
Lots of care is taken to try to make the results reproducible. Each
test is run for multible "rounds", where we try to make each round be
"not too short" in order to be significant wrt timer accuracy, but
also "not to long" to make the probability of some other random event
happening on the system (interrupts, other process scheduled, etc)
during the round less likely.
The current target round time is 4 msecs, which was picked without
rigour, but seems small wrt e.g. scheduler time.
For each test we then run the calculated round size for 60 seconds,
and then report the performance based on the minimal time of one
round. The model here is that any random stuff that happens during a
round can only slow it down, there is nothing that can make it go
faster, so the minimal time is the best estimate of how fast one round
goes.
The result is not ideal, even on a "idle" system the results vary
from round to round, but the variation seems to be less than 1%.
So, any performance difference reported by this test over 1% is
probably statistically significant.
Additionally the tests can be run with or without threads being
initialized. The script tests/gobject/run-performance.sh makes
it easy to produce a performance report for the current checkout.
https://bugzilla.gnome.org/show_bug.cgi?id=557100
Diffstat (limited to 'tests/markups')
0 files changed, 0 insertions, 0 deletions