From: Asymptotically Approaching Relaxation <feoh@cosmic.com>
Subject: Re: Pre-Processed maiil splitting under Gnus?
Date: 12 Jan 1999 02:57:10 -0500 [thread overview]
Message-ID: <ub1zl0rkix.fsf@magrathea.cosmic.com> (raw)
In-Reply-To: Stainless Steel Rat's message of "11 Jan 1999 17:23:25 -0500"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> "AAR" == Asymptotically Approaching Relaxation <feoh@cosmic.com> writes:
>
> AAR> (Note: I'm NOT slamming Gnus here. It's elisp, and given the number
> AAR> of sexpr's it has to eval per message filtered I think it does a
> AAR> *fine* job. It's just that every time I go to read my mail, it gets
> AAR> more and more painful every day to spend 5+ minutes watching Gnus go
> AAR> *chuggachugga*)
>
> 5 *MINUTES*? Gnus and FSF Emacs 19.34 on old 486 DX2-50 with 12Mb RAM,
> running Windows 95, would split a 250-message mail spool file in under 30
> seconds. This was using nnml, the slowest-writing backend available to
> Gnus, on a VFAT filesystem, one of the slowest filesystems available on any
> OS running on the Intel architecture.
>
> I think there is something seriously wrong with your system, not Gnus.
To answer my own question:
I'm seeing a total performance turnaround once I re-wrote my .gnus
file and minimized the length and complexity of the regexes I'm
filtering on.
I'd written the thing in the early days before I got used to how emacs
groks regexes, and was being *extremely* paranoid about full
hostnames, etc.
-Chris
____________________________________________________________________
|Chris Patti|ICQ#16333120|feoh@cosmic.com|Home #:(617)625-3194|JAPH|
|"I have opposable thumbs, and I can buy a rifle. I don't need to |
| run from anything." -Todd Finney |
next prev parent reply other threads:[~1999-01-12 7:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <feoh@cosmic.com>
1999-01-11 22:08 ` Asymptotically Approaching Relaxation
1999-01-11 23:51 ` Richard Coleman
1999-01-12 7:00 ` Asymptotically Approaching Relaxation
1999-01-15 0:53 ` using multiple Summary buffer formats Alfred J Correira
1999-01-15 10:23 ` Kai.Grossjohann
1999-01-15 10:35 ` Lee Willis
1999-01-15 11:13 ` Kai.Grossjohann
[not found] ` <lzww2o21ez.fsf@landlord.gbdirect.co.uk>
[not found] ` <vaf7luon2dv.fsf@ramses.cs.uni-dortmund.de>
1999-01-15 12:34 ` Kai.Grossjohann
1999-01-15 13:04 ` Lee Willis
1999-01-15 14:27 ` Karl Kleinpaste
1999-01-19 14:54 ` Jack Vinson
1999-01-19 15:15 ` Lee Willis
[not found] ` <m3iuedcuua.fsf@peorth.gweep.net>
1999-01-12 7:57 ` Asymptotically Approaching Relaxation [this message]
1999-01-12 16:02 ` Pre-Processed maiil splitting under Gnus? Kai.Grossjohann
1999-01-12 16:38 ` Hrvoje Niksic
1999-01-12 17:00 ` M-x gnus-filter-mail-at-warp-10 (was: Re: Pre-Processed maiil splitting under Gnus?) Asymptotically Approaching Relaxation
1999-01-12 17:35 ` Kai.Grossjohann
1999-01-12 18:42 ` Asymptotically Approaching Relaxation
1999-01-13 22:35 ` Kai.Grossjohann
1999-01-12 20:49 ` M-x gnus-filter-mail-at-warp-10 (was: " Jari Aalto+mail.procmail
1999-01-13 22:32 ` Kai.Grossjohann
1999-01-13 23:21 ` Hrvoje Niksic
1999-01-12 17:21 ` Pre-Processed maiil splitting under Gnus? Lars Magne Ingebrigtsen
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=ub1zl0rkix.fsf@magrathea.cosmic.com \
--to=feoh@cosmic.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).