From: Kevin Atkinson <kevina@gnu.org>
To: gcc@gcc.gnu.org, Jerry Quinn <jlquinn@optonline.net>
Subject: Re: Slow memcmp for aligned strings on Pentium 3
Date: Sun, 06 Apr 2003 22:17:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0304061413430.1075-100000@kevin-pc.atkinson.dhs.org> (raw)
In-Reply-To: <16015.39995.61148.812914@gargle.gargle.HOWL>
On Sat, 5 Apr 2003, Jerry Quinn wrote:
> Kevin Atkinson writes:
> > On Fri, 4 Apr 2003, Jerry Quinn wrote:
> >
> > > I just tried the same benchmark on a Pentium 4 out of curiosity. Slightly
> > > different results:
> > >
> > > Memory compare int:
> > > 10000
> > > 130000
> > > Speed up: 0.076923
> > > Memory compare 15 bytes:
> > > 10000
> > > 370000
> > > Speed up: 0.027027
> > > Memory compare 16 bytes:
> > > 20000
> > > 330000
> > > Speed up: 0.060606
> > > Memory compare 64 bytes:
> > > 10000
> > > 1040000
> > > Speed up: 0.009615
> > > Memory compare 256 bytes:
> > > 20000
> > > 2300000
> > > Speed up: 0.008696
> > >
> > > Perhaps this is to be expected since the routine uses shifts.
> >
> > The shift are only used in the case size is not divisible by 4. It seams
> > that on the Pentium 4 cmps is the way to go. You might also want to
> > increase the number of loop iterations to get more meaning full results
> > due the limited precision of clock().
>
> Adding iterations didn't change the relative scores significantly. It
> still loses big on P4. It also loses big on Athlon. Here are Athlon
> results using the later version you posted with 10x iterations:
>
> jlquinn@smaug:~/gcc/test$ gcc3.3 -O3 -fomit-frame-pointer -march=athlon cmps.c
> jlquinn@smaug:~/gcc/test$ ./a.out
> Memory compare 15 bytes:
> 310000
> 5810000
> Speed up: 0.053356
> Memory compare 16 bytes:
> 300000
> 5290000
> Speed up: 0.056711
> Memory compare 64 bytes:
> 460000
> 13770000
> Speed up: 0.033406
> Memory compare 256 bytes:
> 470000
This is extremely interesting. Does anyone have any documentation on cmps
behavior on P4 and Athlon? It could be that the processor is somehow
"caching" the results of cmps. Maybe it has to do with the fact that the
strings are all 0 except for the end or because the strings do not change.
Or maybe cmps is just extremely fast, but how? Or it could be that the
loop needs unrolling for better pipeline performance. I don't have a P4
or Athlon so if someone could play around with my code by testing by
testing some of my theories I would appreciate it.
I just ran the test on a Pentium MMX and i got similar results as I did
for my P3. So at very least it seams that something similar to my code is
the way to go for Pentiums up to P3.
---
http://kevin.atkinson.dhs.org
next prev parent reply other threads:[~2003-04-06 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 17:13 Jerry Quinn
2003-04-04 17:29 ` Kevin Atkinson
2003-04-06 5:54 ` Jerry Quinn
2003-04-06 22:17 ` Kevin Atkinson [this message]
2003-04-07 17:30 ` Jerry Quinn
-- strict thread matches above, loose matches on Subject: below --
2003-04-04 14:33 Bonzini
2003-04-04 13:18 Roger Sayle
2003-04-04 14:51 ` Kevin Atkinson
2003-04-04 17:08 ` Kevin Atkinson
2003-04-04 18:58 ` Marcel Cox
2003-04-04 19:27 ` Kevin Atkinson
2003-04-04 6:22 Kevin Atkinson
2003-04-04 8:52 ` Zack Weinberg
2003-04-04 15:16 ` Kevin Atkinson
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=Pine.LNX.4.44.0304061413430.1075-100000@kevin-pc.atkinson.dhs.org \
--to=kevina@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jlquinn@optonline.net \
/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).