From: Abhishek Kumar <abhishekkumar8222@gmail.com>
To: abhishekkumar8222@gmail.com
Cc: git@vger.kernel.org, stolee@gmail.com, jnareb@gmail.com
Subject: [GSOC] Blog about weeks 4, 5
Date: Tue, 7 Jul 2020 07:54:25 +0530 [thread overview]
Message-ID: <20200707022425.GA1649@Abhishek-Arch> (raw)
In-Reply-To: <20200706182213.GA51227@Abhishek-Arch>
Hello everyone!
Over the last two weeks, I have worked on refining the performance
report on generation numbers. Here are our conclusions:
- Corrected Commit Dates With Monotonically Offset (i.e. generation
number v5) performs better than topological levels but is still walks
too many commits when compared with Corrected Commit Dates.
Number of commits walked (git merge-base v4.8 v4.9, on linux repository):
Topological Level : 635579
Corrected Commit Date : 167468
Corrected Commit Date With Monotonic Offset: 506577
As such, I am expecting that we will store Corrected Commit Date in an
additional chunk (called "generation data chunk") and store topological
levels into CDAT. Thus, old Git clients can operate as expected, with
new Git clients using the better generation number.
- Using a new chunk does affect the locality of reference but did not
impact the performance appreciably.
- This does increase the size of commit graph file by nearly 5%.
You can read more in my report [1] and the pull request with
instructions to replicate the results [2].
[1]: https://lore.kernel.org/git/20200703082842.GA28027@Abhishek-Arch/T/#mda33f6e13873df55901768e8fd6d774282002146
[2]: https://github.com/abhishekkumar2718/git/pull/1
I talk a bit more about a patch I worked on, trying to improve
performance of commit graph write using buffers which ultimately did not
work and is dropped. Up next is actually implementing the generation
number and take care of all little details.
https://abhishekkumar2718.github.io/programming/2020/07/05/gsoc-weeks-4-5.html
Feedback and suggestions welcome!
Thanks
- Abhishek
--------
Re-sending this email as I forgot to cc git@vger.kernel.org
next parent reply other threads:[~2020-07-07 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200706182213.GA51227@Abhishek-Arch>
2020-07-07 2:24 ` Abhishek Kumar [this message]
2020-07-13 20:00 ` [GSOC] Blog about weeks 4, 5 Jakub Narębski
2020-07-14 6:23 ` 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
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=20200707022425.GA1649@Abhishek-Arch \
--to=abhishekkumar8222@gmail.com \
--cc=20200617093328.GA1327@abhishek-arch \
--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.
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).