From: spamtrap@koldfront.dk (Adam Sjøgren)
Subject: Time to display *Article*, regression from 0.14 to 0.16
Date: Fri, 28 Mar 2003 09:51:06 +0100 [thread overview]
Message-ID: <87znnfho1x.fsf@virgil.koldfront.dk> (raw)
Hi.
I recently went from Oort Gnus 0.14 to 0.16.
Now, when I want to read a long email (nnml, stored locally), say 1000
lines (that has two long URLs on each line, btw.) 0.16 takes apprx. 14
seconds (!) from the time I type SPC to the buffer is displayed,
hogging the CPU.
I tried switching back to 0.14 - exactly same configuration - and the
long email in question displays almost instantly (less than one second
delay).
I see the same behaviour for all long emails. I don't feel any speed
difference on small emails (maybe it's there but less noticable, I
don't know).
This is on a Pentium 4, 2.4 GHz running Linux.
Did something get immensely slower between 0.14 and 0.16, did
something change so I need to change my configuration, or what gives?
I tried looking back a couple of hundred articles here to see if
anyone reported something similar, but didn't see it, so here I am.
If you want more information, tell me what and I'll try to deliver.
Best regards,
Adam
--
"Hvilken sanning, Måns, är sann?" Adam Sjøgren
asjo@koldfront.dk
next reply other threads:[~2003-03-28 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 8:51 Adam Sjøgren [this message]
2003-03-28 17:03 ` Jesper Harder
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=87znnfho1x.fsf@virgil.koldfront.dk \
--to=spamtrap@koldfront.dk \
/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).