| commit | bab45861b7b9d62c3a98fdad76973550f0d0f9d9 | [log] [tgz] |
|---|---|---|
| author | Dave Borowitz <dborowitz@google.com> | Tue May 01 12:31:48 2018 -0400 |
| committer | Dave Borowitz <dborowitz@google.com> | Fri May 18 11:17:49 2018 -0400 |
| tree | 1441d3b558b1b30f4f315b3211299fdfb76f2bc6 | |
| parent | d0f48dbccfebb6ed0ed04c713b2280ed35940695 [diff] |
Optionally persist ChangeNotesCache Loading ChangeNotes into the ChangeNotesCache should generally be pretty fast when the underlying git repository storage is fast, but there are some situations where that is not the case: * The repo hasn't been GC'ed in a while, so may contain a lot of loose objects. * On googlesource.com using the JGit DFS backend, when GC has happened recently and the DFS block cache is cold. These problems are particularly noticeable on a cold server start. As an optional optimization, allow persisting the ChangeNotesCache. For installations where cache loading latency hasn't proven to be a problem, it may not be worth the disk space, but we think it will make a difference for googlesource.com. Writing the necessary protos was a bit of work, but actually the marginal cost of tweaking fields should be relatively low, and any change should cause a small test to fail, so we should be able to detect any changes as they arise. I explicitly chose to reuse existing serialization mechanisms where possible (ProtobufCodecs, JSON), to limit the size of this change. This is just cache data, so it's not like it has to be particularly pretty or long-lasting. This change is not intended to indicate we are giving up on optimizing loading ChangeNotes from storage, but is more of a bandaid for fixing performance problems in production today. Change-Id: I1ffe15fe56b6822b7f9af55635b063793e66d6fd
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 IRC channel on freenode is #gerrit. An archive is available at: echelog.com.
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 --recursive 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 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.