4d5047e0e7
The main use of the performance test is to run it for two (or more) commits
and compare the results. Doing that manually, is cumbersome.
Add a (very hacky) script to help with that. For usage, see the comment
on top of the script.
Example:
# first:
meson build -Dprefix=/tmp/glib/ -Db_lto=true --buildtype release -Ddebug=true
# then:
GLIB_PERFORMANCE_FACTOR=17.06 \
PERF='perf stat -r 4 -B' \
PATCH="2.80.0..th/performance" \
COMMITS="2.79.3 2.80.0" \
/tmp/performance-run.sh -s 1 property-get property-set
This will build the requested $COMMITS and print something like:
...
>>> combined result > /tmp/glib-performance-output.all
Running test property-get
property-get: Property get per second: 35742719 37208288 (+4.1%)
Running test property-set
property-set: Property set per second: 32341232 36942399 (+14.2%)
Running test property-get
property-get: Property get per second: 36934401 37143479 (+0.566%)
Running test property-set
property-set: Property set per second: 38046387 38165548 (+0.313%)
Running test property-get
property-get: Property get per second: 34759576 36359761 (+4.6%)
Running test property-set
property-set: Property set per second: 35262505 37651733 (+6.78%)
Running test property-get
property-get: Property get per second: 37014537 32870906 (-11.2%)
Running test property-set
property-set: Property set per second: 36633026 38216846 (+4.32%)
Performance counter stats for './build/gobject/tests/performance/performance -s 1 property-get property-set' (4 runs):
1,312.18 msec task-clock:u # 1.000 CPUs utilized ( +- 4.82% )
0 context-switches:u # 0.000 /sec
0 cpu-migrations:u # 0.000 /sec
121 page-faults:u # 92.213 /sec ( +- 0.24% )
5,221,701,009 cycles:u # 3.979 GHz ( +- 2.61% )
19,035,814,175 instructions:u # 3.65 insn per cycle ( +- 0.00% )
4,335,306,010 branches:u # 3.304 G/sec ( +- 0.00% )
13,031 branch-misses:u # 0.00% of all branches ( +- 4.17% )
TopdownL1 # 10.3 % tma_backend_bound
# 5.3 % tma_bad_speculation
# 11.4 % tma_frontend_bound
# 73.1 % tma_retiring ( +- 2.15% )
[1] 1.3127 +- 0.0634 seconds time elapsed ( +- 4.83% )
[2] 1.2631 +- 0.0253 seconds time elapsed ( +- 2.00% )
property-get: Property get per second: 35742719 , 36934401 , 34759576 , 37014537 ; 37208288 , 37143479 , 36359761 , 32870906 ;
property-set: Property set per second: 32341232 , 38046387 , 35262505 , 36633026 ; 36942399 , 38165548 , 37651733 , 38216846 ;
|
||
|---|---|---|
| .gitlab-ci | ||
| .reuse | ||
| docs | ||
| fuzzing | ||
| gio | ||
| girepository | ||
| glib | ||
| gmodule | ||
| gobject | ||
| gthread | ||
| LICENSES | ||
| m4macros | ||
| po | ||
| subprojects | ||
| tests | ||
| tools | ||
| .clang-format | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .lcovrc | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| glib.doap | ||
| INSTALL.md | ||
| meson_options.txt | ||
| meson.build | ||
| NEWS | ||
| README.md | ||
| SECURITY.md | ||
GLib
GLib is the low-level core library that forms the basis for projects such as GTK and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.
The official download locations are: https://download.gnome.org/sources/glib
The official web site is: https://www.gtk.org/
Installation
See the file ‘INSTALL.md’. There is separate and more in-depth documentation for building GLib on Windows.
Supported versions
Upstream GLib only supports the most recent stable release series, the previous stable release series, and the current development release series. All older versions are not supported upstream and may contain bugs, some of which may be exploitable security vulnerabilities.
See SECURITY.md for more details.
Documentation
API documentation is available online for GLib for the:
Discussion
If you have a question about how to use GLib, seek help on GNOME’s Discourse
instance. Alternatively, ask a question
on StackOverflow and tag it glib.
Reporting bugs
Bugs should be reported to the GNOME issue tracking system. You will need to create an account for yourself. You may also submit bugs by e-mail (without an account) by e-mailing incoming+gnome-glib-658-issue-@gitlab.gnome.org, but this will give you a degraded experience.
Bugs are for reporting problems in GLib itself, not for asking questions about how to use it. To ask questions, use one of our discussion forums.
In bug reports please include:
- Information about your system. For instance:
- What operating system and version
- For Linux, what version of the C library
- And anything else you think is relevant.
- How to reproduce the bug.
- If you can reproduce it with one of the test programs that are built
in the
tests/subdirectory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded.
- If you can reproduce it with one of the test programs that are built
in the
- If the bug was a crash, the exact text that was printed out when the crash occurred.
- Further information such as stack traces may be useful, but is not necessary.
Contributing to GLib
Please follow the contribution guide to know how to start contributing to GLib.
Patches should be submitted as merge requests to gitlab.gnome.org. If the patch fixes an existing issue, please refer to the issue in your commit message with the following notation (for issue 123):
Closes: #123
Otherwise, create a new merge request that introduces the change. Filing a separate issue is not required.