| commit | 41f46c881ec01129a61b4051af7cdbc169a9383a | [log] [tgz] |
|---|---|---|
| author | Nasser Grainawi <nasser.grainawi@linaro.org> | Fri Jul 21 17:25:57 2023 -0600 |
| committer | Nasser Grainawi <nasser.grainawi@linaro.org> | Wed Jul 26 14:11:54 2023 -0600 |
| tree | b278cfa9fb4b1cd26573fe864ed8e51d4067a712 | |
| parent | 7376523edfcf16b8f42a864738a1e1f8eac72cb8 [diff] |
Use RoaringBitmap instead of BitSet in TagSet Leverage the RoaringBitmap libary [1] to optimize usage and storage of TagSets. This makes a significant improvement (see below) particularly for repos with a combination of many tags and many non-tag/non-change refs. Also increment the git_tags cache version since the storage format is changed. This change intends to only do a straightforward replacement of BitSet and does not attempt any further optimizations RoaringBitmap may provide. Performance comparison: These numbers were gathered after running `git ls-remote` against a very large repo with 1.3M refs (including ~375K tags and ~26.5K other non-skippable refs). | | BitSets | RoaringBitmap (this change) | | h2 PageStore heap memory used | 2.5 GB | 155 MB | | disk size of git_tags cache | 1.5 GB | 58 MB | | runtime | 5.75 min | 5.5 min | Further, with Gerrit's heapLimit (java -Xmx) setting set to 26g, the BitSet implementation was not able to successfully execute the ls-remote, whereas the RoaringBitmap implementation continued to perform with a consistent runtime down to at least 16g and even still worked at 10g (lowest tested) but runtime then increased to 6.5 min. [1] https://github.com/RoaringBitmap/RoaringBitmap Change-Id: Ief36b7bb2312899a64efb9a10565b3d095ed5584 Release-Notes: Reduced memory and storage needs for TagSet by using RoaringBitmaps
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.