public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Evolution 2.2.3 Filtering Time (Too Long!)
Date: Thu, 25 Aug 2005 09:12:09 +0800	[thread overview]
Message-ID: <1124932329.16628.8.camel@localhost> (raw)
In-Reply-To: <1124900477.15428.2.camel@localhost>

The evidence I have for this is a bit "vague" being more of an
impression that processing is faster, but it seems that evo runs one
filter on a message, then the next, and so on.  If you can almalgamate
rules that do similar functions (i.e., copy messages to the same
directory) into one compound rule, they seem to run faster as they are
dealing with fewer, albeit more complex filters.

It would be nice to know exactly how the filtering mechanism works for
this.

To re-iterate, the majority of delays (after implementing stop rules per
filter etc) are outside evo's control, particularly online spam checking
and these are areas its not really possible to do much about if you need
the functionality (and I certainly do!).  

BillK


On Wed, 2005-08-24 at 12:21 -0400, fire-eyes wrote:
> On Wed, 2005-08-24 at 09:06 +0800, W.Kenworthy wrote:
> > 3. use a compound filter rather than separate ones (this assumes there
> > is less overhead doing this - subjectively it does seem quicker)
> 
> Thanks for the tips. The above one is the only one I don't really
> understand, can you elaborate a bit?
> 

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-25  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-23 11:25 [gentoo-user] Evolution 2.2.3 Filtering Time (Too Long!) fire-eyes
2005-08-24  1:06 ` W.Kenworthy
2005-08-24  1:37   ` Owen Ford
2005-08-24 16:21   ` fire-eyes
2005-08-25  1:12     ` W.Kenworthy [this message]
2005-08-24  2:39 ` Ow Mun Heng

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=1124932329.16628.8.camel@localhost \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.org \
    /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