Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel M. <xt@nm.ru>
Subject: Re: Gnus is very slow in displaying headers.
Date: Tue, 24 Aug 2004 10:30:33 -0700	[thread overview]
Message-ID: <jotmi0tfqk9neaj9sthmnratpum8vgu57p@4ax.com> (raw)
In-Reply-To: <uu0ut2l91.fsf@xpediantsolutions.com>


>The problem is mostly likely due to your setting for
>gnus-summary-line-format.  This is a string that describes the fields
>displayed for each line of the summary buffer.  Internally, gnus
>compiles this string into an elisp expression that inserts an article
>into the buffer.  The approach is infinitely customizable but not very
>optimizable.  You might look in the manual under 'Summary Buffer
>Lines' to see if can identify a simplier string; one that meets your
>requirements yet offers better performance.

It indeed improves somewhat the performance but it is still far
from usable. Here are the settings I have used and the time to load
headers into a summary buffer (the group contained 12000
headers):

(setq gnus-summary-line-format "") - 1 min. and 8 sec.
(setq gnus-summary-line-format "\n") - 1 min. and 8 sec.
(setq gnus-summary-line-format "%s\n") - 1 min. 37 sec.

Setting gnus-show-threads to nil doesn't make any noticable
difference.

Using any other formatting options pushes loading time still 
higher. No matter what I tried, it doesn't take less then 2 minutes
to load the group, even if the most basic usable summary formatting
line was used.

Is there are other ways to speed up the process?

BTW, my computer's specs are:

CPU: Athlon 1333, RAM: 768MB.

Daniel.





  reply	other threads:[~2004-08-24 17:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23  3:40 Daniel M.
2004-08-23 12:12 ` Jorge Godoy
2004-08-24  6:02   ` Daniel M.
2004-08-23 20:22     ` Jorge Godoy
2004-08-24  4:49 ` Kevin Greiner
2004-08-24 17:30   ` Daniel M. [this message]
2004-08-24  9:31     ` Kai Grossjohann
2004-08-24 19:44       ` Daniel M.
2004-08-24 12:05         ` Kai Grossjohann
2004-08-24 13:35           ` Derrell.Lipman
2004-08-25  6:08             ` Daniel M.
2004-08-25  7:14             ` Kai Grossjohann
2004-08-25  6:26           ` Daniel M.
2004-08-24 20:54             ` Andrew A. Raines
2004-08-25  8:57             ` Kai Grossjohann
2004-08-24 20:07 ` Jesper Harder
2004-08-25  6:34   ` Daniel M.
2004-08-26 14:50 ` ignotus
2004-08-27 23:24   ` Daniel M.

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=jotmi0tfqk9neaj9sthmnratpum8vgu57p@4ax.com \
    --to=xt@nm.ru \
    /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).