All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Iozone <capps@iozone.org>
Cc: Neil Brown <neilb@suse.de>,
	cel@citi.umich.edu, wli@holomorphy.com,
	nfs@lists.sourceforge.net
Subject: Re: Re: An interesting performance thing ?
Date: Thu, 15 Dec 2005 09:49:01 -0500	[thread overview]
Message-ID: <20051215144901.GD14973@fieldses.org> (raw)
In-Reply-To: <020a01c60133$3d8fc530$1500000a@americas.hpqcorp.net>

On Wed, Dec 14, 2005 at 10:51:40PM -0600, Iozone wrote:
>        One of the interesting things I noticed is that the general
>    purpose hash_long() function may not be as optimal
>    as a more focused hash_IP_addr() function might be,
>    even if GOLDEN were GOLDEN :-) And, trying
>    to smash 128 bit IPV6 addresses into a 8 bit hash
>    value, that is somehow uniformly distributed, well,
>    that's going to be quite a neat trick, and making it
>    work for 32 bit, 64, and 128 bit objects, with uniform
>    distribution over a variable number of output bits,
>    is approaching magical.

I'm not so pessimistic, but I'm also not expert enough about hash
functions to know how much magic is reasonable to expect out of a good
one.  Time to pull out Knuth, maybe.

There might also be an argument for experimenting with different data
structures.  I'd expect high temporal locality--in typical situations a
server with lots of clients may have only a few that are active at a
particular time--so one of those balanced trees that migrates recently
looked-up items to the top might be helpful.

Aside from seeing the race condition triggered, have you done any
profiling to make sure this is actually a big problem, even with the
current worst-case linear-search behaviour?

--b.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-12-15 14:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 18:22 An interesting performance thing ? Iozone
2005-12-14 22:26 ` Neil Brown
2005-12-14 22:46   ` Chuck Lever
2005-12-14 23:47     ` Iozone
2005-12-15  0:02       ` Neil Brown
2005-12-15  0:43         ` Chuck Lever
2005-12-15  0:57           ` Neil Brown
2005-12-15  0:59             ` Chuck Lever
2005-12-16 10:15           ` Aurélien Charbon
2005-12-16 14:23             ` Iozone
2005-12-15  2:32         ` J. Bruce Fields
2005-12-15  4:51           ` Iozone
2005-12-15 14:49             ` J. Bruce Fields [this message]
2005-12-15 15:36               ` Iozone
2005-12-15 16:14                 ` J. Bruce Fields
2005-12-15 16:41                   ` Iozone
2005-12-15 17:07                     ` J. Bruce Fields
2005-12-16  1:25                   ` Neil Brown
2005-12-16  3:59                     ` Iozone
2005-12-14 22:50   ` Iozone
2005-12-15  2:22 ` J. Bruce Fields

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=20051215144901.GD14973@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=capps@iozone.org \
    --cc=cel@citi.umich.edu \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=wli@holomorphy.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.