| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Change-Id: Ifd7cac3f646ecef2e8b12079771c01af410691bb
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Takes two qbs repo states, runs callgrind and massif on different phases
of the build process for each of them and informs the user of the
relative performance of these operations.
I suggest running this tool before committing anything that could
conceivably impact performance. Note that we have similar regression
detection functionality on our build machines, but it's better to spot
such problems before pushing a change.
Example output (for commits 04df1532c4 and f53d724eec building qbs itself):
========== Performance data for Resolving ==========
Old instruction count: 1931242543
New instruction count: 1457438375
Relative change: -25 %
Old peak memory usage: 1710721 Bytes
New peak memory usage: 1509879 Bytes
Relative change: -12 %
========== Performance data for Rule Execution ==========
Old instruction count: 2924308821
New instruction count: 2890322188
Relative change: -2 %
Old peak memory usage: 2520740 Bytes
New peak memory usage: 2488058 Bytes
Relative change: -2 %
========== Performance data for Null Build ==========
Old instruction count: 572213104
New instruction count: 517813513
Relative change: -10 %
Old peak memory usage: 1964455 Bytes
New peak memory usage: 1774279 Bytes
Relative change: -10 %
Change-Id: I1f05c647d204b6cacf3539c8ecbf13633b757cf7
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
|
| |
|
|
|
|
|
| |
This amends commit 7c82e9f3.
Change-Id: Ie01db1f28856fa16edee67aaf033c7150ecb197c
Reviewed-by: Christian Kandeler <christian.kandeler@digia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Incremental builds are the likeliest source of problems, as well as the
one that is the hardest to reproduce. This new tool turns a given project
into a quasi-autotest by checking out random commits and doing incremental
builds on them. In case of a build error that is not reproducible with
a clean build, it aborts and reports the offending sequence of commits.
Any qbs project that comes in a git repository is supported.
Change-Id: I9f6f9172ce03140341ed25859092a8ed32d4a17d
Reviewed-by: Joerg Bornemann <joerg.bornemann@digia.com>
|
|
|
Change-Id: I412793e868919a9ac99611616f292e7047f1ebcf
|
