From: Jeff King <peff@peff.net>
To: Ben Peart <peartben@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Ben Peart <benpeart@microsoft.com>,
git@vger.kernel.org, pclouds@gmail.com, chriscool@tuxfamily.org,
Johannes.Schindelin@gmx.de, alexmv@dropbox.com
Subject: Re: [PATCH v1 1/4] fastindex: speed up index load through parallelization
Date: Mon, 20 Nov 2017 10:38:46 -0500 [thread overview]
Message-ID: <20171120153846.v5b7ho42yzrznqoh@sigill.intra.peff.net> (raw)
In-Reply-To: <20171120142035.bfwu24oegw27ucs3@sigill.intra.peff.net>
On Mon, Nov 20, 2017 at 09:20:35AM -0500, Jeff King wrote:
> Out of curiosity, have you tried experimenting with any high-performance
> 3rd-party allocator libraries? I've often wondered if we could get a
> performance improvement from dropping in a new allocator, but was never
> able to measure any real benefit over glibc's ptmalloc2. The situation
> might be different on Windows, though (i.e., if the libc allocator isn't
> that great).
Just linking with tcmalloc, like:
diff --git a/Makefile b/Makefile
index ee9d5eb11e..4f299cd914 100644
--- a/Makefile
+++ b/Makefile
@@ -1018,7 +1018,7 @@ BUILTIN_OBJS += builtin/worktree.o
BUILTIN_OBJS += builtin/write-tree.o
GITLIBS = common-main.o $(LIB_FILE) $(XDIFF_LIB)
-EXTLIBS =
+EXTLIBS = -ltcmalloc
GIT_USER_AGENT = git/$(GIT_VERSION)
seems to consistently show about 30% speedup on p0002:
Test HEAD^ HEAD
--------------------------------------------------------------------------------------
0002.1: read_cache/discard_cache 1000 times 0.19(0.18+0.01) 0.13(0.12+0.01) -31.6%
I don't think we really even need a patch for it. You should be able to
just build with:
make EXT_LIBS=-ltcmalloc
I can't think of any real advantage to a Makefile knob except
discoverability.
-Peff
next prev parent reply other threads:[~2017-11-20 15:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 14:17 [PATCH v1 0/4] Speed up index load through parallelization Ben Peart
2017-11-09 14:17 ` [PATCH v1 1/4] fastindex: speed " Ben Peart
2017-11-10 4:46 ` Junio C Hamano
2017-11-13 16:42 ` Ben Peart
2017-11-14 1:10 ` Junio C Hamano
2017-11-14 14:31 ` Ben Peart
2017-11-14 15:04 ` Junio C Hamano
2017-11-14 15:40 ` Ben Peart
2017-11-15 1:12 ` Junio C Hamano
2017-11-15 4:16 ` Ben Peart
2017-11-15 4:40 ` Junio C Hamano
2017-11-20 14:01 ` Ben Peart
2017-11-20 14:20 ` Jeff King
2017-11-20 15:38 ` Jeff King [this message]
2017-11-20 23:51 ` Ramsay Jones
2017-11-21 0:45 ` Ben Peart
2017-11-09 14:17 ` [PATCH v1 2/4] update-index: add fastindex support to update-index Ben Peart
2017-11-09 14:17 ` [PATCH v1 3/4] fastindex: add test tools and a test script Ben Peart
2017-11-09 14:17 ` [PATCH v1 4/4] fastindex: add documentation for the fastindex extension Ben Peart
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=20171120153846.v5b7ho42yzrznqoh@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=alexmv@dropbox.com \
--cc=benpeart@microsoft.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peartben@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).