| commit | 2fd651a1a67678274bc1b8d2352d28ce8f2210d8 | [log] [tgz] |
|---|---|---|
| author | Adithya Chakilam <achakila@codeaurora.org> | Wed Oct 20 14:04:49 2021 -0500 |
| committer | Adithya Chakilam <achakila@codeaurora.org> | Thu Nov 04 18:06:44 2021 +0000 |
| tree | ab42543229b51529ffc82ebb4accf0cfb3255bd4 | |
| parent | ef5c300f3fb4c49924834bbe5759305eb338e47a [diff] |
Disable auto flushing during offline Lucene indexing Current indexing process waits for the indexed changes to be flushed, which writes the in-memory segments to disk. Flushing makes those updates available to the searcher threads. This is helpful during online reindexing because we want searches to have up-to-date data. However, in case of offline indexing this creates frequent unnecessary flushes. It is ideal to flush all the in-memory segments at the end during offline indexing process since there are no searches happening on index and also lets us skip doing many segment merges. This change disables auto flushing during init/reindex commands and the online reindexing behaviour is unchanged. On a test site with ~160K changes, this change brought down the runtime of reindex command from ~5mins to ~3mins when disk-caches are pre-populated from previous reindex run and with no disk-caches there was a reduction from ~49mins to ~45mins. Number of flushes decreased from ~120K to 81 in both the cases. Number of segment merges decreased from ~13k and ~2k to 6 during pre-populated and empty disk-caches respectively. Flushes now only happen based on the index.<name>.ramBufferSize and index.<name>.maxBufferedDocs settings. Change-Id: I6094a98e8cdb2c3c3b1be328db19b0920c0bc895
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 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.