From: Andrew Haley <aph@redhat.com>
To: "Giovanni Bajo" <rasky@develer.com>
Cc: <michael.meeks@novell.com>, <gcc@gcc.gnu.org>
Subject: Re: Large, modular C++ application performance ...
Date: Sat, 30 Jul 2005 17:24:00 -0000 [thread overview]
Message-ID: <17131.47092.25498.822504@zapata.pink> (raw)
In-Reply-To: <019e01c5950b$a7ddff90$bf03030a@trilan>
Giovanni Bajo writes:
> michael meeks <michael.meeks@novell.com> wrote:
>
> > I've been doing a little thinking about how to improve OO.o startup
> > performance recently; and - well, relocation processing happens to be
> > the single, biggest thing that most tools flag.
> >
> > Anyhow - so I wrote up the problem, and a couple of potential
> > solutions / extensions / workarounds, and - being of a generally
> > clueless nature, was hoping to solicit instruction from those of a more
> > enlightened disposition.
> >
> > All input much appreciated; no doubt my terminology is irritatingly up
> > the creek, hopefully the sentiment will win through.
> >
> > http://go-oo.org/~michael/OOoStartup.pdf
One thing I don't understand is the formula where you write linking
time is proprortional to the log of the total number of symbols. Does
this come from drepper's paper, or somewhere else?
Andrew.
next prev parent reply other threads:[~2005-07-30 17:24 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 [this message]
2005-08-01 9:45 ` michael meeks
2005-08-01 12:18 ` Steven Bosscher
2005-08-02 9:22 ` michael meeks
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=17131.47092.25498.822504@zapata.pink \
--to=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=michael.meeks@novell.com \
--cc=rasky@develer.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).