From: Daniel M. <xt@nm.ru>
Subject: Re: Gnus is very slow in displaying headers.
Date: Fri, 27 Aug 2004 16:24:54 -0700 [thread overview]
Message-ID: <8kcvi0ld29ea7m37jab6pfrdkoobg7tgpt@4ax.com> (raw)
In-Reply-To: <871xhu54y9.fsf@my.gnus.org>
>Yes, the sad fact is that Gnus is that slow and it doesn't matter what
>you do you can't bring it up to the ,,normal speed'' (which means under
>1 second), not even close to it.
Maybe one day X/Emacs would be fitted with Common Lisp backend
having a native-code compiler - then probably the speed would improve
sufficiently for Gnus to be usable with bigger groups: for the time being,
though, it seems that Gnus is not for me :(.
I don't understand, though, why summary buffers have to be generated
afresh every time you enter a group - it seems to me that generating
it once, saving to HD and then adding/removing chunks from it when
needed (for example, when new headers arrive, some articles are read
etc.) should speed the things up immensely. Also, it looks to me like
a good idea to have a command line option which will cause regeneration
of summary buffers (if summary buffers are saved to HD). Then, if
user decides to change summary buffer's format line, he can say, for
example: 'xemacs --gnus-regenerate-summary-buffers', then go and
have a (long) lunch, after which he can come back and start reading
his dose of news without waiting for regeneration of summary buffers.
>I tried to do that with Gnus, trimmed down all the features I thought I
>didn't absolutely need etc but of course it was still extremely slow.
>But I sticked with it because it was so much more configurable, I saw at
>the time that with an Emacs based software the limit is my imagination,
>while with Mutt / slrn / etc the limit is the configuration options the
>developers decide to impelement.
Well, you can add whatever options you want by simply modifying
slrn's source code - some people have done exactly that (see
http://www.xs4all.nl/~thunder7/, for example). Maybe it is easier
to do in elisp, but if you are well familiar with GNU's development
chain (which I, at least, am not), it shouldn't be a big problem.
>You may know already what happened to me. While mutt / slrn maximizes
>the time you have for reading by not ,,interrupting you'' with long
>computations, Gnus minimizes the time you will need to read the messages
>by having so much ,,time-saving'' features (adapting scoring is a
>godsend). And after you experienced both, I can assure you that the
>latter feels better. ;)
Don't think it will work for me - by the time the group is loaded, the
time allocated for my news reading would probably be up :^).
Daniel.
prev parent reply other threads:[~2004-08-27 23:24 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.
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. [this message]
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=8kcvi0ld29ea7m37jab6pfrdkoobg7tgpt@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).