From: David Turner <dturner@twopensource.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] On watchman support
Date: Mon, 01 Dec 2014 15:45:50 -0500 [thread overview]
Message-ID: <1417466750.20544.2.camel@leckie> (raw)
In-Reply-To: <CACsJy8DayFy83JijrkgST5rAbNsst-dgqaP-ebpWXoGKPtp7sA@mail.gmail.com>
On Fri, 2014-11-28 at 18:13 +0700, Duy Nguyen wrote:
> On Wed, Nov 19, 2014 at 1:12 AM, David Turner <dturner@twopensource.com> wrote:
> >> 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.
>
> Cityhash looks less appealing to me. For one thing it's C++ so linking
> to C can't be done. I could add a few "extern "C"" to make it work.
> But if we plan to support it eventually, cityhash must support C out
> of the box.
>
> Then cityhash does not support case-insensitive hashing. I had to make
> a CityHash32i version based on CityHash32. It's probably my bugs
> there, but performance is worse (~120ms) than original hashmap.c
> (90ms). Enabling sse4.2 helps a bit, but still worse. Using the
> case-sensitive version in place for memihash and strihash does make
> cityhash win over hashmap.c, around 50ms (with or without sse4.2). But
> that's still not as good as your version (~35ms)..
Can you post your CityHash32i?
Have you tried this C port of Cityhash?
https://github.com/santeri-io/cityhash-c
next prev parent reply other threads:[~2014-12-01 20:45 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
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 [this message]
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=1417466750.20544.2.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 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.