public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gnu dot org" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs-regex@sources.redhat.com
Subject: [Bug regex/501] transit_state is slow
Date: Thu, 11 Nov 2004 09:20:00 -0000 [thread overview]
Message-ID: <20041111092047.12651.qmail@sourceware.org> (raw)
In-Reply-To: <20041104085106.501.bonzini@gnu.org>
------- Additional Comments From bonzini at gnu dot org 2004-11-11 09:20 -------
Here is a testcase. Timings taken on a PPC G4 at 1.5 GHz
time perl -e 'print "A" x 10000' | ./sed -n '/[A-Z].*[0-9]$/p'
without patch: 1.98s
with patch: 1.89s
time perl -e 'print "A" x 30000' | ./sed -n '/[A-Z].*[0-9]$/p'
without patch: 17.59s
with patch: 17.11s
In this case, regex complexity is quadratic. This is a savings of 2.7%; I
remember seeing slightly higher figures on x86.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=501
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2004-11-11 9:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 8:51 [Bug regex/501] New: " bonzini at gnu dot org
2004-11-10 10:55 ` [Bug regex/501] " bonzini at gnu dot org
2004-11-10 14:05 ` drepper at redhat dot com
2004-11-10 14:19 ` bonzini at gnu dot org
2004-11-11 9:20 ` bonzini at gnu dot org [this message]
2004-11-13 12:59 ` bonzini at gnu dot org
2004-11-13 13:00 ` bonzini at gnu dot org
2004-12-01 17:01 ` bonzini at gnu dot org
2004-12-10 16:50 ` bonzini at gnu dot org
2004-12-20 10:21 ` bonzini at gnu dot org
2004-12-20 10:22 ` bonzini at gnu dot org
2004-12-27 16:40 ` drepper 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=20041111092047.12651.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs-regex@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).