From: Brian Edmonds <edmonds@cs.ubc.ca>
Cc: joseph@cis.ohio-state.edu
Subject: Re: External delivery: Pros and cons
Date: Wed, 15 Nov 1995 07:38:25 -0800 [thread overview]
Message-ID: <199511151538.HAA00082@edmonds.home.cs.ubc.ca> (raw)
In-Reply-To: <umt68gmfgrg.fsf@honsu.cis.ohio-state.edu> (message from Sudish Joseph on 15 Nov 1995 03:01:39 -0500)
> Date: 15 Nov 1995 03:01:39 -0500
>
> Cons:
One con you forgot that used to bother me a lot: when you filter
incoming messages, you end up with one (potentially large: perl) process
per message. If you're on a system like mine where I retrieve mail via
UUCP once per hour, all those processes starting up at once can put a
serious strain on the system. I have blown out my virtual space once in
the past when I was only running with 20M.
I find splitting the mail inside emacs is pretty quick, unless you've
got hundreds of messages, and far kinder on my hard drive and system
performance. As it is, just punting everything through sendmail at once
produces a noticable lag.
Brian. http://www.cs.ubc.ca/spider/edmonds
next prev parent reply other threads:[~1995-11-15 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-15 8:01 Sudish Joseph
1995-11-15 15:38 ` Brian Edmonds [this message]
1995-11-16 4:37 ` Scott Blachowicz
2002-10-20 20:13 Unknown
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=199511151538.HAA00082@edmonds.home.cs.ubc.ca \
--to=edmonds@cs.ubc.ca \
--cc=joseph@cis.ohio-state.edu \
/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).