Gnus development mailing list
 help / color / mirror / Atom feed
From: Ken Raeburn <raeburn@cygnus.com>
Cc: ding@ifi.uio.no
Subject: Re: Long time to exit summary buffer, possible speed enhancement?
Date: 30 Sep 1996 11:57:43 -0400	[thread overview]
Message-ID: <tx1lodsyozs.fsf@cygnus.com> (raw)
In-Reply-To: Steinar Bang's message of 30 Sep 1996 07:37:15 +0100


Steinar Bang <sb@metis.no> writes:

> In those newsgroup, with big gaps, I see slow startup time (slow for
> the number of articles unmarked + number of new).
> 
> Are there any traces I can make to find out where it uses its time?

As Lars said earlier in this thread:

> Anyways, range handling isn't all that slow, so the ~10 second delay
> probably is caused by something else.  Try `(setq debug-on-quit t)'
> and then `C-g' when things "hang" (sorta).  The resulting backtrace
> should tell you which function is being slow.

I recommend doing this but hitting C-g a few times during the slow
bits.  If it's in the same code most of the time you trap into the
debugger, that's a more convincing case for that code being the time
sink.  If you do it only once, you could get a traceback in a part
that's actually very efficient if your timing happens to be poor.

Ken


  reply	other threads:[~1996-09-30 15:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-09-27 20:28 Shane Holder
1996-09-28 20:08 ` Lars Magne Ingebrigtsen
1996-09-29  9:50   ` Ken Raeburn
1996-09-30 15:21     ` Shane Holder
1996-09-30 15:51       ` Ken Raeburn
1996-09-29 13:09   ` Hallvard B Furuseth
1996-09-29 21:36     ` Ken Raeburn
1996-09-30  6:37       ` Steinar Bang
1996-09-30 15:57         ` Ken Raeburn [this message]
1996-09-30  6:34     ` Steinar Bang
1996-10-01  3:39     ` Lars Magne Ingebrigtsen
1996-10-01 14:59       ` Colin Rafferty
1996-10-04 10:00         ` Hallvard B Furuseth
1996-10-04  9:54       ` Hallvard B Furuseth
1996-10-01  7:07 ` Kai Grossjohann

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=tx1lodsyozs.fsf@cygnus.com \
    --to=raeburn@cygnus.com \
    --cc=ding@ifi.uio.no \
    /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 NNTP newsgroup(s).