From: David Turner <dturner@twopensource.com>
To: Duy Nguyen <pclouds@gmail.com>, gitster@pobox.com
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] On watchman support
Date: Tue, 18 Nov 2014 13:12:40 -0500 [thread overview]
Message-ID: <1416334360.27401.10.camel@leckie> (raw)
In-Reply-To: <CACsJy8BfxP7KF1XF29BOgC6XhO8iAy-ycEoLkDG5rn6TYH_DrA@mail.gmail.com>
On Tue, 2014-11-18 at 17:48 +0700, Duy Nguyen wrote:
> > My patches are not the world's most beautiful, but they do work. I
> > think some improvement might be possible by keeping info about tracked
> > files in the index, and only storing the tree of ignored and untracked
> > files separately. But I have not thought this through fully. In any
> > case, making use of shared memory for the fs_cache (as some of your
> > other patches do for the index) would definitely save time.
>
> By the way, what happened to your sse optimization in refs.c? I see
> it's reverted but I didn't follow closely to know why.
I don't know why either -- it works just fine. There was a bug, but I
fixed it. Junio?
> Or will you go
> with cityhash now.. I ask because you have another sse optimization
> for hashmap on your watchman branch and that could reduce init time
> for name-hash. Name-hash is used often on case-insensitive fs (less
> often on case-sensitive fs).
Cityhash would be better, because it has actual engineering effort put
into it; what I did on my branch is a hack that happens to work
decently. As the comment notes, I did not spend much effort on tuning
my implementation. Also, Cityhash doesn't require SSE, so it's more
portable.
> I did a simple test and your optimization could init name-hash (on
> webkit) in 35ms, while unmodified hashmap took 88ms. Loading index on
> this machine took 360ms for reference (probably down too 100ms with
> index-helper running, when that 88ms starts to become significant).
OK, that sounds like a big win.
next prev parent reply other threads:[~2014-11-18 18:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 12:49 [RFC] On watchman support Duy Nguyen
2014-11-13 5:05 ` Torsten Bögershausen
2014-11-13 12:22 ` Duy Nguyen
2014-11-15 7:24 ` Torsten Bögershausen
2014-11-18 0:25 ` David Turner
2014-11-18 10:48 ` Duy Nguyen
2014-11-18 18:12 ` David Turner [this message]
2014-11-18 20:55 ` Junio C Hamano
2014-11-18 21:12 ` David Turner
2014-11-18 21:26 ` Junio C Hamano
2014-11-19 1:46 ` Jeff King
2014-11-28 11:13 ` Duy Nguyen
2014-12-01 20:45 ` David Turner
2014-11-19 15:26 ` Paolo Ciarrocchi
2014-11-19 16:43 ` David Turner
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=1416334360.27401.10.camel@leckie \
--to=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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).