public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tim Prince <tprince@computer.org>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Howard Chu <hyc@highlandsun.com>,  gcc@gcc.gnu.org
Subject: Re: [Fwd: performance with gcc -O0/-O2]
Date: Tue, 27 Nov 2007 16:09:00 -0000	[thread overview]
Message-ID: <474C255B.3090205@computer.org> (raw)
In-Reply-To: <84fc9c000711270536i799dc2c7u64d931ebdf213f57@mail.gmail.com>

Richard Guenther wrote:
> On Nov 27, 2007 2:23 PM, Howard Chu <hyc@highlandsun.com> wrote:
>> A bit of a minor mystery. Not a problem, just a curiosity. If someone knew off
>> the top of their head a reason for it, that'd be cool, but otherwise no sweat.
> 
> I'd try -Os, you might run into ICache limitations.
Try -Os with and without setting -mpreferred-stack-boundary=4 (or
whatever value you currently have).  Watch memory usage, cache
evictions, etc. while running.
> 
> Richard.
> 
>> -------- Original Message --------
>> Subject: Re: commit: ldap/servers/slapd connection.c daemon.c proto-slap.h
>> syncrepl.c
>> Date: Tue, 27 Nov 2007 05:17:04 -0800
>> From: Howard Chu <hyc@symas.com>
>> To: OpenLDAP-devel@openldap.org
>> References: <200711261603.lAQG3R7e010741@cantor.openldap.org>
>> <474AFA54.6080805@symas.com>    <474B0620.8030706@symas.com>
>> <474B92F5.50306@symas.com>
>>
>> Howard Chu wrote:
>>> Howard Chu wrote:
>>>> Howard Chu wrote:
>>>>> For reference, the peak throughput with back-null on the previous code was
>>>>> only 7,800 auths/sec (with 8 client threads). With this patch it's 11,140
>>>>> auths/sec.
>> Those numbers are for Windows Server 2003 x86_64 on a Celestica A8440 with 4
>> Opteron 875s, using OpenLDAP compiled with gcc 4.3.0. The following numbers
>> are for Linux 2.6.23.1 x86_64, on the same machine, compiled first with gcc
>> 4.1.2 and then later with gcc 4.2.2. There's no disk I/O in these tests.
>>
>>>>> In both cases the throughput declines as more client threads are
>>>>> used. (Compare to 35,553 auths/sec for the same machine running Linux, and no
>>>>> drop in throughput all the way up to hundreds/thousands of connections.)
>>> Re-running on Linux with a non-optimized build, peaked at 40,101 auths/sec. (I
>>> guess HEAD has sped up a bit more in the past week or so...)
>> OK, this is odd. The code compiled without optimization peaks at 40K auths/sec
>> at around 124-132 client threads. The code compiled with -O2 peaks at 37K sec
>> at around 128 client threads.
>>
>> The -O2 build is faster from about 4 to 24 client threads. From 28 on up, the
>> nonoptimized code is faster at every load level. I was originally using gcc
>> 4.1.2 but I'm seeing the same result now using gcc 4.2.2. Also, slapd is only
>> configured with 8 worker threads in all of these tests. Strange that whatever
>> optimizations the compiler has generated speeds things up for lighter load,
>> but works against it under heavier load.
>> --
>>    -- Howard Chu
>>    Chief Architect, Symas Corp.  http://www.symas.com
>>    Director, Highland Sun        http://highlandsun.com/hyc/
>>    Chief Architect, OpenLDAP     http://www.openldap.org/project/
>>

  reply	other threads:[~2007-11-27 14:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-27 14:19 Howard Chu
2007-11-27 14:19 ` Richard Guenther
2007-11-27 16:09   ` Tim Prince [this message]
2007-11-27 17:59   ` Howard Chu
2007-11-27 15:46 ` Andrew Haley
2007-11-27 15:51 J.C. Pizarro
2007-11-27 20:45 ` Howard Chu
     [not found] <474C1A62.9000300@highlandsun.com.suse.lists.egcs>
     [not found] ` <18252.8713.124845.847654@zebedee.pink.suse.lists.egcs>
2007-11-27 16:47   ` Andi Kleen
2007-11-27 18:13     ` Andrew Haley

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=474C255B.3090205@computer.org \
    --to=tprince@computer.org \
    --cc=gcc@gcc.gnu.org \
    --cc=hyc@highlandsun.com \
    --cc=richard.guenther@gmail.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).