Gnus development mailing list
 help / color / mirror / Atom feed
From: Eze Ogwuma <typhoon@dircon.co.uk>
Cc: ding@gnus.org
Subject: Re: Gnus as slow as molasses
Date: 25 Apr 1998 06:04:07 +0100	[thread overview]
Message-ID: <m3hg3ize48.fsf@localhost.localdomain> (raw)
In-Reply-To: Hrvoje Niksic's message of "17 Apr 1998 13:12:14 +0200"


Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Eze Ogwuma <typhoon@dircon.co.uk> writes:
> 
> > string-match                               264      17.647
> > directory-files                            261      17.447
> > match-string                               168      11.230
> 
> Does this mean that `directory-files' is called 261 times?  (I'm not
> familiar with the output of `profile-keystrokes'.)

I'm sorry, I don't know either. I was told to try this by Hrvoje
Niksic, see the message below. I couldn't find any mention of it in
the XEmacs manuals.

> Anyways, I think the culprit is `nnheader-article-to-file-alist',
> which is Slow in huge groups if you have jka-compr loaded.

With or without this opening the first article is very slow. I've
found that not having comresssion in the .emacs file decreases the
time by ~33.3% however this is not the ~99.4% needed to remove the
problem.


Hrvoje Niksic <hniksic@srce.hr> writes:

> Eze Ogwuma <typhoon@dircon.co.uk> writes:
> 
> > This additional information was sent to someone as a reply.
> > 
> > The problem isn't opening the group as I rarely select more that 100
> > articles. It's selecting the first article once I'm in the group.
> > 
> > I have this in my .gnus file so I get to choose which article to
> > select:
> > ;; Don't select the first article automatically
> > (setq  gnus-auto-select-first nil)   
> > 
> > Whichever article I select then takes about 10-15 seconds to
> > display. All articles selected after that are almost instantaneous
> > whether they are above or below the first article.
> 
> Under XEmacs 20.4 you can use `M-x profile-key-sequence', press a key
> (say RET in the Group buffer), and get the results using
> `M-x profile-results'.  It should give you an idea of where the time
> is being spent.
> 

-- 
Eze Ogwuma


  parent reply	other threads:[~1998-04-25  5:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-17  4:21 Eze Ogwuma
1998-04-17  6:11 ` Eze Ogwuma
1998-04-17  9:49   ` Kai Grossjohann
1998-04-17 15:29     ` Eze Ogwuma
1998-04-17 11:12   ` Hrvoje Niksic
1998-04-17 16:20     ` Eze Ogwuma
1998-04-24 20:29       ` Lars Magne Ingebrigtsen
1998-04-17 18:38     ` Felix Lee
1998-04-17 19:46       ` Karl Kleinpaste
1998-04-17 19:03         ` Felix Lee
1998-04-25  5:04     ` Eze Ogwuma [this message]
1998-04-25 13:12       ` Lars Magne Ingebrigtsen
1998-04-25 14:49         ` Eze Ogwuma
     [not found]           ` <m3hg3idjz7.fsf@sparky.gnus.org>
1998-04-25 17:46             ` Eze Ogwuma
1998-04-25 23:50               ` Lars Magne Ingebrigtsen
1998-04-26  1:12                 ` Eze Ogwuma
1998-04-26 12:27                   ` Lars Magne Ingebrigtsen
1998-04-26 18:59                     ` Eze Ogwuma
1998-04-26 15:03                   ` Karl Kleinpaste
1998-04-26 18:58                     ` Eze Ogwuma
1998-04-27 14:17       ` Hrvoje Niksic

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=m3hg3ize48.fsf@localhost.localdomain \
    --to=typhoon@dircon.co.uk \
    --cc=ding@gnus.org \
    /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).