| commit | c11ff7e35bc6c60501938c69db60ab3d5fb5bb52 | [log] [tgz] |
|---|---|---|
| author | Edwin Kempin <ekempin@google.com> | Thu Apr 25 13:11:33 2024 +0000 |
| committer | Edwin Kempin <ekempin@google.com> | Fri Apr 26 06:29:13 2024 +0000 |
| tree | d8fd33b503f5144f71192bf27f4d8d808e03cff0 | |
| parent | 491337d70cad8f3e25ae3477a7723021d395a480 [diff] |
Record duration of performance events in nanos instead of in millis If the duration is recorded in millis all operations that take less than 1ms are recorded with 0ms. This means they will have the exact same start and end times because the start time is computed by (end time minus duration), although start and end time have nanosecond precision. This is bad when visualising events in a gantt chart as events that have the exact same start and end time (and hence a 0 duration) cannot be shown. This is confusing when analysing performance logs because expected events do not show up (it's unclear if they do not show up because they were not executed or because they were faster than 1ms). Notes, TimerContext already records the elapsed time in nanos and provides them with TimeUnit.NANOSECONDS to the timers. While we are here, make the formatting of how the elapsed time is shown in debug logs everywhere consistent (with a space between the number and the "ms"). Release-Notes: Record duration of performance events in nanos (instead of in millis) Change-Id: I8ad36b03b4dd79a6fe975920ad7b33700bf0e87f Signed-off-by: Edwin Kempin <ekempin@google.com>
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update && apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 8 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8
To run a Ubuntu 20.04 based Gerrit image:
docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.