git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Kaartic Sivaraam" <kaartic.sivaraam@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git <git@vger.kernel.org>,
	"Derrick Stolee" <derrickstolee@github.com>
Subject: Re: Can I use CRoaring library in Git?
Date: Mon, 25 Jul 2022 18:11:15 -0400	[thread overview]
Message-ID: <Yt8VA22wz9BlzzMN@nand.local> (raw)
In-Reply-To: <CAPOJW5w+6jaHJe8FBVzjAfRBATYuV=+uv4HeA_fpRKFbRtKXcw@mail.gmail.com>

On Mon, Jul 18, 2022 at 02:27:59PM +0530, Abhradeep Chakraborty wrote:
> > I assume that Abhradeep will want to pursue some format redesign as part
> > of the transition, though, at least to see if changing the format beyond
> > a version bump and new compression scheme is worthwhile.
>
> I haven't thought much about it until now. As far as I think we don't
> need Xor Flag anymore.

I think that would be an interesting experiment to run. I suspect that
XOR-compression is helping us quite a lot with on-disk file size with
EWAH bitmaps, but that may or may not be true with Roaring.

If Roaring can compress the same selection of bitmaps to a comparable
size without the additional layer of XOR-offsets, then I think they are
additional complexity that can be eschewed for now.

(Keep in mind, we can always revisit that decision if we decide that we
want to add XOR compression back in through another version bump. But it
would be good to make backwards-incompatible changes as infrequently as
possible. So this is a good opportunity for us to be as thorough in our
experimentation as possible).

Thanks,
Taylor

  reply	other threads:[~2022-07-25 22:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 13:50 Can I use CRoaring library in Git? Abhradeep Chakraborty
2022-07-16 14:16 ` Ævar Arnfjörð Bjarmason
2022-07-16 16:26   ` Abhradeep Chakraborty
2022-07-17 12:25     ` Kaartic Sivaraam
2022-07-17 22:00       ` Junio C Hamano
2022-07-17 22:25         ` Taylor Blau
2022-07-18  8:57           ` Abhradeep Chakraborty
2022-07-25 22:11             ` Taylor Blau [this message]
2022-07-17 14:43 ` Derrick Stolee
2022-07-18 11:13 ` Jakub Narębski
2022-07-18 11:38   ` Abhradeep Chakraborty
2022-07-18 13:38     ` Ævar Arnfjörð Bjarmason
2022-07-18 11:48 ` Abhradeep Chakraborty
2022-07-18 12:18   ` Derrick Stolee
2022-07-18 13:15     ` Abhradeep Chakraborty
2022-07-18 21:48     ` brian m. carlson
2022-07-25 22:14     ` Taylor Blau
2022-07-25 22:35       ` rsbecker
2022-07-25 23:37         ` Taylor Blau
2022-07-21  4:07 ` Abhradeep Chakraborty
2022-07-21  6:12   ` Junio C Hamano
2022-07-21 12:14     ` Derrick Stolee
2022-07-21 13:51       ` Ævar Arnfjörð Bjarmason
2022-07-21 14:57         ` Abhradeep Chakraborty
2022-07-22 11:07           ` Ævar Arnfjörð Bjarmason

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=Yt8VA22wz9BlzzMN@nand.local \
    --to=me@ttaylorr.com \
    --cc=avarab@gmail.com \
    --cc=chakrabortyabhradeep79@gmail.com \
    --cc=derrickstolee@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kaartic.sivaraam@gmail.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).