From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: git@jeffhostetler.com
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
gitster@pobox.com, peff@peff.net,
"Jeff Hostetler" <jeffhost@microsoft.com>,
git@vger.kernel.org
Subject: Re: [PATCH v5 4/4] read-cache: speed up add_index_entry during checkout
Date: Thu, 6 Apr 2017 00:54:53 +0200 [thread overview]
Message-ID: <20170405225453.2632-1-szeder.dev@gmail.com> (raw)
In-Reply-To: <20170405173809.3098-5-git@jeffhostetler.com>
> Teach add_index_entry_with_check() and has_dir_name()
> to see if the path of the new item is greater than the
> last path in the index array before attempting to search
> for it.
>
> During checkout, merge_working_tree() populates the new
> index in sorted order, so this change saves at least 2
> lookups per file.
I think the performance numbers from the cover letter should be
included here, so they will be included in the history.
> Signed-off-by: Jeff Hostetler <jeffhost@microsoft.com>
next prev parent reply other threads:[~2017-04-05 22:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 17:38 [PATCH v5 0/4] read-cache: speed up add_index_entry git
2017-04-05 17:38 ` [PATCH v5 1/4] p0004-read-tree: perf test to time read-tree git
2017-04-06 20:20 ` René Scharfe
2017-04-06 20:41 ` Jeff Hostetler
2017-04-05 17:38 ` [PATCH v5 2/4] read-cache: add strcmp_offset function git
2017-04-06 14:19 ` SZEDER Gábor
2017-04-06 15:58 ` Jeff Hostetler
2017-04-05 17:38 ` [PATCH v5 3/4] test-strcmp-offset: created test for strcmp_offset git
2017-04-05 22:47 ` SZEDER Gábor
2017-04-06 8:21 ` Johannes Schindelin
2017-04-06 14:25 ` Jeff Hostetler
2017-04-06 20:20 ` René Scharfe
2017-04-06 20:42 ` Jeff Hostetler
2017-04-05 17:38 ` [PATCH v5 4/4] read-cache: speed up add_index_entry during checkout git
2017-04-05 22:54 ` SZEDER Gábor [this message]
2017-04-06 14:05 ` Jeff Hostetler
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=20170405225453.2632-1-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=git@jeffhostetler.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeffhost@microsoft.com \
--cc=peff@peff.net \
/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).