Profiling Gnus (was: Re: Typos...)

[Daniel Pittman <daniel@rimspace.net>]

On Mon, 27 Aug 2001, Simon Josefsson wrote:
> Daniel Pittman <daniel@rimspace.net> writes:
> 
>>> Yeah, currently `g' makes nnfolder/nnml read the mark files and
>>> calculate things, which isn't necessary (it's only necessary if the
>>> marks file is changed).  I'll fix it soon.
>>
>> Oh, good. I was starting to ponder instrumenting Gnus and finding out
>> where it was wasting time on startup; it takes a few tens of seconds
>> (with no progress message even at verbosity 7 -- hint) to do the
>> marks stuff over my 1.1GB of nnml...
> 
> I've added some more messages.  I did not made the optimization I
> thought of before yet, as it would actually be useful if you could
> instrument Gnus to find out where it's spending time, it may suggest
> other functions to optimize.

Well, I am happy enough to do this...

> Please M-x elp-instrument-package RET gnus RET and M-x
> elp-instrument-package RET nn RET.  M-x elp-results RET after starting
> Gnus and after doing `g' would be useful.  Thanks.

...if you will let me in on the secret of getting it to instrument the
functions. :)

I updated to the latest CVS version and removed all the compiled lisp
from gnus/lisp. So far, so good.

So, I can't actually `elp-instrument-package' gnus because it's full of
autoload functions. Fine. I restart, use dired and %m, L all the .el is
the Gnus directory...

...which still has a bunch of autoloads hanging around and now won't
actually start.

*sigh*

So, if anyone can tell me how to do this profiling, I am quite happy to
do so.

        Daniel

-- 
In addition to my other numerous acquaintances, I have one more intimate
confidant. My depression is the most faithful mistress I have known ---
no wonder, then, that I return the love.
        -- Søren Kierkegaard, _Either/Or_ (1843)