From: git@jeffhostetler.com
To: git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: [PATCH v7 0/3] read-cache: speed up add_index_entry
Date: Fri, 7 Apr 2017 21:20:44 +0000 [thread overview]
Message-ID: <20170407212047.64950-1-git@jeffhostetler.com> (raw)
From: Jeff Hostetler <jeffhost@microsoft.com>
Version 7 addresses size_t and casting issues in strcmp_offset()
and replaces shell test function with an awk expression to make
the perf test run faster.
================
Teach add_index_entry_with_check() and has_dir_name()
to avoid index lookups if the given path sorts after
the last entry in the index.
This saves at least 2 binary searches per entry.
This improves performance during checkout and read-tree because
merge_working_tree() and unpack_trees() processes a list of already
sorted entries.
Jeff Hostetler (3):
read-cache: add strcmp_offset function
p0004-read-tree: perf test to time read-tree
read-cache: speed up add_index_entry during checkout
Makefile | 1 +
cache.h | 1 +
read-cache.c | 66 +++++++++++++++++++++++-
t/helper/.gitignore | 1 +
t/helper/test-strcmp-offset.c | 64 +++++++++++++++++++++++
t/perf/p0004-read-tree.sh | 117 ++++++++++++++++++++++++++++++++++++++++++
t/t0065-strcmp-offset.sh | 11 ++++
7 files changed, 259 insertions(+), 2 deletions(-)
create mode 100644 t/helper/test-strcmp-offset.c
create mode 100755 t/perf/p0004-read-tree.sh
create mode 100755 t/t0065-strcmp-offset.sh
--
2.9.3
next reply other threads:[~2017-04-07 21:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 21:20 git [this message]
2017-04-07 21:20 ` [PATCH v7 1/3] read-cache: add strcmp_offset function git
2017-04-08 10:11 ` Jeff King
2017-04-07 21:20 ` [PATCH v7 2/3] p0004-read-tree: perf test to time read-tree git
2017-04-08 10:36 ` Jeff King
2017-04-10 13:34 ` Jeff Hostetler
2017-04-07 21:20 ` [PATCH v7 3/3] read-cache: speed up add_index_entry during checkout git
2017-04-08 9:40 ` Jeff King
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=20170407212047.64950-1-git@jeffhostetler.com \
--to=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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.