After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 91871 - Need a profiling howto for gnome
Need a profiling howto for gnome
Status: RESOLVED FIXED
Product: website
Classification: Infrastructure
Component: wiki.gnome.org
current
Other Linux
: Normal normal
: ---
Assigned To: Malcolm Tredinnick
Malcolm Tredinnick
Depends on:
Blocks: 91873
 
 
Reported: 2002-08-28 12:55 UTC by Telsa Gwynne
Modified: 2007-07-09 19:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Telsa Gwynne 2002-08-28 12:55:46 UTC
We need a GNOME 2 profiling document listing profiling tools
and how to use them and then how to fix them. There has beem
some discussion of this on gnome-list and gnome-hackers in 
early August 2002: thread mutated from a subject line of
"Re: Some questions and tips" to "Speed suggestions" which
has some great stuff from michael and others about programs
and apps to use. 

Something which consolidates this lot into a list of general
"app name: what it does: what it doesn't do: how to use it:
examples: where to get it" tips would be really good. 

and the developer faq could then link to it too.
Comment 1 Malcolm Tredinnick 2002-09-02 01:22:11 UTC
This is mine. I have started on it. The topic has expanded to include
debugging aids, as well as profiling, since there are about half a
billion secret environment variables you can set to get output from
various modules.
Comment 2 Telsa Gwynne 2002-09-02 09:55:54 UTC
Well, if it wants to grow into debugging, this is very cool.
Then the developer faq can just point at it for debugging too.

Thanks so much, Malcolm. 
Comment 3 Peter Williams 2002-09-04 05:24:27 UTC
Malcolm: I'd be happy to work on sections of this if you don't mind
sending me bits of your work-in-progress. Especially if you're going
to cover general debugging, hopefully I can be useful in talking about
gdb or strace. Well, the latter also being useful for profiling.
Comment 4 Malcolm Tredinnick 2002-09-04 05:34:23 UTC
Absolutely! All help gratefully accepted, Peter. I worked a bit more
on this document last night and the plan is for more this evening. I
will send you what I have by then tomorrow for you to look over and we
can plan the division of the remaining work.

Thanks. :-)
Comment 5 Peter Williams 2002-09-16 04:50:54 UTC
Hey, what's the status on this?
Comment 6 Christophe Fergeau 2003-07-20 12:09:49 UTC
Something which could be mentionned in such a doc are Soeren's slides
from his GU4DEC talk (if they are available online)
Malcolm, is the stuff you started to work on available somewhere online ?
Comment 7 Malcolm Tredinnick 2003-07-20 17:49:57 UTC
I still have what I was writing, but it isn't checked in or available
anywhere yet (it will eventually go into the gnome-devel-docs module).
I'll reread what I have and check it in. 

I'm all in favour of incorporating other peoples' junk as well as my
own: we might as well all sink or swim together.
Comment 8 Federico Mena Quintero 2004-09-23 23:11:09 UTC
Ping?
Comment 9 Callum McKenzie 2004-09-27 03:01:53 UTC
I've just added an optimization section to d.g.o, so we definitely have
somewhere to put it. Malcolm, if you don't want to spend any more time on it,
I'd be prepared to go over it and upload it.
Comment 10 Malcolm Tredinnick 2004-09-27 03:20:40 UTC
I'll dig out what I have. Hmmm .. wonder where it is? :-|
Comment 11 Quim Gil 2006-01-06 01:13:58 UTC
What is the status of this, please?

Moving this bug to he live.gnome.org component since this is the current platform for documentation.
Comment 12 Murray Cumming 2007-07-09 19:17:44 UTC
http://live.gnome.org/GnomePerformance
seems to cover this.