From: Abhishek Kumar <abhishekkumar8222@gmail.com>
To: git@vger.kernel.org
Cc: jnareb@gmail.com, stolee@gmail.com
Subject: [GSOC] Blog about week 6
Date: Tue, 14 Jul 2020 12:02:36 +0530 [thread overview]
Message-ID: <20200714063236.GB10242@Abhishek-Arch> (raw)
Hello everyone!
Over the last week, I started implementing generation number v2. Based
on the performance numbers and subsequent discussion, we have decided to
use generation data chunk approach, storing topological levels into CDAT
and corrected commit date offsets into GDAT chunk. Do note that we are
maintaining backward compatibility using topological level, not with
monotonic offsets.
I also found a performance regression with `commit-graph write
--reachable --changed_path` that sneaked in along with the patch on
moving generation and graph positions into commit-slab.
https://abhishekkumar2718.github.io/gsoc/2020/07/12/gsoc-week-6.html
https://github.com/gitgitgadget/git/pull/676
> Yes, I pushed without signing off or a cover letter. It's still a work
> in progress.
Thanks
Abhishek
next reply other threads:[~2020-07-14 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 6:32 Abhishek Kumar [this message]
2020-07-17 22:49 ` [GSOC] Blog about week 6 Jakub Narębski
2020-07-21 13:27 ` Abhishek Kumar
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200714063236.GB10242@Abhishek-Arch \
--to=abhishekkumar8222@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=stolee@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox