public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xoswald at debian dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/11607] New: strstr function very slow.
Date: Mon, 17 May 2010 09:27:00 -0000 [thread overview]
Message-ID: <20100517092705.11607.xoswald@debian.org> (raw)
I think tere are a huge regression for the strstr function between version 2.7
and 2.10.
In our code we use the 'strstr' function a lot and became to the fact that
strstr is having a strange behaviour.
I attach 2 file so you can test it.
$gcc test-strstr.c -o test
$time test 10000
Some results (User Time):
=================
Ubuntu 8.04 : 10s (glibc 2.7)
Ubuntu 9.04 : 1m20s (glibc 2.10)
Ubuntu 10.04 : 1m20s (glibc 2.10)
Debian lenny : 8s (glibc 2.7)
Debian Squeeze : 1m10s (glibc 2.10)
The results are the same on AMD64 and i386 architectures.
--
Summary: strstr function very slow.
Product: glibc
Version: 2.10
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: xoswald at debian dot org
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=11607
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2010-05-17 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 9:27 xoswald at debian dot org [this message]
2010-05-17 9:28 ` [Bug libc/11607] " xoswald at debian dot org
2010-05-17 9:29 ` xoswald at debian dot org
2010-05-17 9:33 ` xoswald at debian dot org
2010-05-17 9:42 ` jakub at redhat dot com
2010-05-17 12:14 ` eblake at redhat dot com
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=20100517092705.11607.xoswald@debian.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).