From: michael meeks <michael.meeks@novell.com>
To: Steven Bosscher <stevenb@novell.com>
Cc: gcc@gcc.gnu.org, Andrew Haley <aph@redhat.com>,
Giovanni Bajo <rasky@develer.com>
Subject: Re: Large, modular C++ application performance ...
Date: Tue, 02 Aug 2005 09:22:00 -0000 [thread overview]
Message-ID: <1122974530.25747.34.camel@linux.site> (raw)
In-Reply-To: <200508011418.38489.stevenb@novell.com>
On Mon, 2005-08-01 at 14:18 +0200, Steven Bosscher wrote:
> On Monday 01 August 2005 11:44, michael meeks wrote:
> > However - the log(s) term is rather irrelevant to my argument :-)
>
> Not really. Maybe the oprofile results for the linker show that the
> behavior is worse, or maybe better - who knows :-)
> Have you looked at any profiles btw? Just for the curious...
Yes - identifying the linker and relocation processing as the root
cause of the problem isn't just a stab in the dark :-)
This flgas up as the no.1 (individual) performance killer with whatever
profiling tools you use eg.:
* vtune
* speedprof
* instrumenting top/tail of dlopen calls
etc. :-)
Regards,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
next prev parent reply other threads:[~2005-08-02 9:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 19:49 michael meeks
2005-07-29 20:19 ` Florian Weimer
2005-07-30 13:26 ` Nix
2005-07-30 13:36 ` Giovanni Bajo
2005-07-30 17:24 ` Andrew Haley
2005-08-01 9:45 ` michael meeks
2005-08-01 12:18 ` Steven Bosscher
2005-08-02 9:22 ` michael meeks [this message]
2005-08-01 9:39 ` michael meeks
2005-08-01 15:55 ` H. J. Lu
2005-08-02 9:59 ` michael meeks
2005-08-02 13:57 ` H. J. Lu
2005-08-02 16:15 ` michael meeks
2005-08-03 3:07 ` PATCH: Add export to linker map (Re: Large, modular C++ application performance ...) H. J. Lu
2005-08-01 16:59 ` Large, modular C++ application performance Dan Nicolaescu
2005-07-30 15:19 dank
2005-08-01 9:53 ` michael meeks
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=1122974530.25747.34.camel@linux.site \
--to=michael.meeks@novell.com \
--cc=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=rasky@develer.com \
--cc=stevenb@novell.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).