From: Han-Wen Nienhuys <hanwen@google.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>,
Taylor Blau <me@ttaylorr.com>,
git@vger.kernel.org
Subject: Re: What is the status of GSoC 2022 work on making Git use roaring bitmaps?
Date: Mon, 31 Jul 2023 19:46:18 +0200 [thread overview]
Message-ID: <CAFQ2z_P2HkT8grAFk=6Mr05rJRfsh_sXypVFPyHr0v5xkcjYTA@mail.gmail.com> (raw)
In-Reply-To: <85tty8afvy.fsf@gmail.com>
On Sat, Mar 25, 2023 at 6:40 PM Jakub Narębski <jnareb@gmail.com> wrote:
> >>> Abhradeep promised[1] that he'd include some performance work in his
> >>> next version of that series. I think the main things we'd be interested
> >>> in are:
> >>>
> >>> - Does using Roaring provide a file-size advantage over
> >>> EWAH-compressed bitmaps?
I modified JGit to write Roaring bitmaps instead of EWAH bitmaps. The
resulting difference in file sizes are small, and actually favor EWAH:
$ ls -l {ewah-repos,roaring-repos}/*.git/objects/pack/*.bitmap
-r--r----- 1 hanwen primarygroup 26257386 Jul 31 15:04
ewah-repos/android-pfb.git/objects/pack/pack-b14c35ec7fc3bb20884abe51a81c832be5983fdc.bitmap
-r--r----- 1 hanwen primarygroup 27621579 Jul 31 15:20
roaring-repos/android-pfb.git/objects/pack/pack-b14c35ec7fc3bb20884abe51a81c832be5983fdc.bitmap
-r--r----- 1 hanwen primarygroup 1037356 Jul 31 14:46
ewah-repos/gerrit.git/objects/pack/pack-fe46c7f96a2910f5775a2ff3bef7e4fa0e779f91.bitmap
-r--r----- 1 hanwen primarygroup 1242608 Jul 31 14:45
roaring-repos/gerrit.git/objects/pack/pack-fe46c7f96a2910f5775a2ff3bef7e4fa0e779f91.bitmap
--
Han-Wen Nienhuys - Google Munich
I work 80%. Don't expect answers from me on Fridays.
--
Google Germany GmbH, Erika-Mann-Strasse 33, 80636 Munich
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Liana Sebastian
next prev parent reply other threads:[~2023-07-31 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 19:26 What is the status of GSoC 2022 work on making Git use roaring bitmaps? Jakub Narębski
2023-03-23 20:26 ` Taylor Blau
2023-03-23 22:01 ` Jakub Narębski
2023-03-24 3:48 ` Abhradeep Chakraborty
2023-03-25 17:40 ` Jakub Narębski
2023-07-31 17:46 ` Han-Wen Nienhuys [this message]
2023-07-31 20:18 ` Taylor Blau
2023-08-01 11:26 ` Han-Wen Nienhuys
2023-08-01 11:34 ` Jakub Narębski
2023-08-01 11:54 ` Han-Wen Nienhuys
2023-08-01 13:17 ` Jakub Narębski
2023-08-01 17:33 ` Taylor Blau
2023-08-01 17:43 ` Jakub Narębski
2023-08-01 17:31 ` Taylor Blau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFQ2z_P2HkT8grAFk=6Mr05rJRfsh_sXypVFPyHr0v5xkcjYTA@mail.gmail.com' \
--to=hanwen@google.com \
--cc=chakrabortyabhradeep79@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=me@ttaylorr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).