From: Harry Putnam <reader@newsguy.com>
Subject: '0.95 /slow to open large (1009K) messages
Date: 14 Jul 1999 04:49:37 -0700 [thread overview]
Message-ID: <m3d7xvwiwe.fsf@satellite.local.lan> (raw)
I've just noticed while opening large cron daemon messages, a very
lengthy pause.
The messages run around 20,000 lines "wc" shows:
$ wc <big-cron
19861 19922 103290
So, app. 1009K of data.
Gnus takes a full minute to open one of these. (timed at 59.6 seconds).
Mutt opens them instantly.
I'm sure gnus is doing a lot more work than mutt, but still this seems
too long. What do other people see when opening a large message? Is
this normal?
next reply other threads:[~1999-07-14 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-14 11:49 Harry Putnam [this message]
1999-07-14 12:03 ` Karl Kleinpaste
1999-07-14 12:21 ` Harry Putnam
1999-07-14 14:52 ` Colin Rafferty
1999-07-14 12:46 ` Andrew Markebo
1999-07-14 15:20 ` Michael Welsh Duggan
1999-07-14 15:34 ` Bruce Z. Lysik
1999-08-27 18:34 ` Lars Magne Ingebrigtsen
1999-07-14 15:27 ` Simon Josefsson
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=m3d7xvwiwe.fsf@satellite.local.lan \
--to=reader@newsguy.com \
/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).