Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76923
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
To: Sebastian Bergmann <sebastian@php.net>
Cc: internals@lists.php.net
In-Reply-To: <53FEE35A.7010402@php.net>
References: <53FEE18E.9070900@php.net>
	 <CAEZPtU6ZJaObDHQ4Qy9X2REEM9+0uneyeDdJXJgQYN2o5zb3_g@mail.gmail.com>
	 <53FEE35A.7010402@php.net>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 28 Aug 2014 18:48:55 +0200
Message-ID: <1409244535.6881.59.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] SipHash
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Thu, 2014-08-28 at 10:07 +0200, Sebastian Bergmann wrote:
> Am 28.08.2014 um 10:04 schrieb Pierre Joye:
> > ext/hash can have it anyway. I did not look at it if it makes sense to
> > use it in other parts.
> 
>  Sorry for not bein more clear: yes, I was thinking about adding it to
>  ext/hash, of course. It might make sense, though, to evaluate whether
>  it can also be used internally. Other languages seem to have switched
>  their hashtable implementation to SipHash.

Try it out. Mind that we are doing quite few more hash operations than
other languages. I doubt barely anybody here has the maths background to
predict impact on hash calculation performance and conflict ratio and
even then only a test and analysis of different benchmarks will tell the
truth.

johannes