Message 186019 - Python tracker

Message186019

Author	lemburg
Recipients	lemburg, pitrou, serhiy.storchaka, vstinner
Date	2013-04-04.09:30:40
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<515D483A.1070609@egenix.com>
In-reply-to	<CAMpsgwY6ayw9JW3dEceXmgMsUaW95TTtoXrgSQN4mt1xyBwXoA@mail.gmail.com>

Content
On 04.04.2013 11:21, STINNER Victor wrote: > > STINNER Victor added the comment: > > By the way, my initial concern was to merge unicode_compare_eq() and > unicode_eq() functions. > > unicode_compare_eq() only uses memcmp(), whereas unicode_eq() checks > if the first byte is different before calling memcmp(). So the > question is to decide which one is faster ;-) The second one was faster a couple of years ago. Things may have changed since then (better compilers, CPUs, etc.). Perhaps you could run a benchmark with increasing sizes of strings, one set with mismatches in the last character, the other with matching strings.

Content

On 04.04.2013 11:21, STINNER Victor wrote:
> 
> STINNER Victor added the comment:
> 
> By the way, my initial concern was to merge unicode_compare_eq() and
> unicode_eq() functions.
> 
> unicode_compare_eq() only uses memcmp(), whereas unicode_eq() checks
> if the first byte is different before calling memcmp(). So the
> question is to decide which one is faster ;-)

The second one was faster a couple of years ago. Things may have
changed since then (better compilers, CPUs, etc.). Perhaps you
could run a benchmark with increasing sizes of strings, one set
with mismatches in the last character, the other with matching
strings.

History
Date	User	Action	Args
2013-04-04 09:30:40	lemburg	set	recipients: + lemburg, pitrou, vstinner, serhiy.storchaka
2013-04-04 09:30:40	lemburg	link	issue17628 messages
2013-04-04 09:30:40	lemburg	create