From: Christian Couder <christian.couder@gmail.com>
To: ZheNing Hu <adlternative@gmail.com>
Cc: "Git List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Hariom verma" <hariom18599@gmail.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [GSoC] Git Blog 7
Date: Mon, 5 Jul 2021 21:09:19 +0200 [thread overview]
Message-ID: <CAP8UFD1_xjJxWA6O8Sx9-AEk5oC62U4GFkt5iRdx8Po_mJzTMg@mail.gmail.com> (raw)
In-Reply-To: <CAOLTT8R_=8Md3vk5yBK4dggq1RKof_6c1tOEtfchbSmYf+gwtA@mail.gmail.com>
On Sun, Jul 4, 2021 at 4:42 PM ZheNing Hu <adlternative@gmail.com> wrote:
>
> My seventh week blog finished:
> The web version is here:
> https://adlternative.github.io/GSOC-Git-Blog-7/
Thanks!
> ## Week7 Performance Testing 2
>
> This week I used performance flame graph at the suggestion of
> my mentor `Christian` to find out where my patch affected the
> performance of `cat-file --batch`. `oid_object_info_extended()`
> takes the largest proportion of time, accounting for `90.28%`
> and `41.60%` in `cat-file --batch` and `cat-file --batch-check`
> respectively. Part of the reason is that `oid_object_info_extended()`
> is called twice in `get_object()` with my patch. I tried to revise its
> logic (`WIP`), the performance is improved when without using
s/when without/when not/
> `--textconv` and `--filters`.
>
> `Ævar Arnfjörð Bjarmason` gave me a good suggestion on
> performance regression: When we use the default format of
> `git cat-file --batch-check` or `git cat-file --batch`, we can
> directly print the meta-data of the object without going through
> the logic of `ref-filter`; When we use other format, use the
> logic in ref-filter.
>
> In addition, `Ævar Arnfjörð Bjarmason` also suggests adding a
> performance test for `git cat-file --batch`, this can help us analyze
> and compare performance changes later.
>
> There are intensive exams in these two weeks, and sometimes the
> response may be delayed.
Ok, no worries!
prev parent reply other threads:[~2021-07-05 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 14:42 [GSoC] Git Blog 7 ZheNing Hu
2021-07-05 19:09 ` Christian Couder [this message]
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=CAP8UFD1_xjJxWA6O8Sx9-AEk5oC62U4GFkt5iRdx8Po_mJzTMg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=adlternative@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hariom18599@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;
as well as URLs for NNTP newsgroup(s).