"... I expect it to reduce memory usage of Evolution with approximately fourty to sixty megabytes of ram, depending on the amount of folders you have ..." http://pvanhoof.be/blog/index.php/2006/07/19/the-first-official-mmap-summ...

fre, 21 07 2006 kl. 22:17 -0700, skrev Otto Rey: > Well, i think that evolution have one or more memory leaks, because > more time you have running, more memory it seems to eat. But it's > true: if you don't use calendar and the other addtional stuff, you > don't need evlotuion, or, if you want, you can turn off several > plugins. > Addtional to memory launch, evolution-connector for M$ Exchange > sucks... it's almost always broken... or half-broken... With some > updates, it's looks like solid but with the next update, it's crash > again... > Whatever... i will profile evolution to see if i found a memory > leak... I think the problem with Evolutions memory use is largely fragmentation not leaking. I'd like to mention that the default Evolution setup in FC loads the Spamassassin plugin which on my machine at least takes up 80megs of memory, replacing that with the bogofilter plugin turned out to be a good decision - I blogged a bit about that adventure* Maybe we can get that plugin upstream as the default for great savings, running a daemon for spam training is probably a tad overkill anyways. * http://lovesunix.net/blog/?p=102

On Sat, 2006-07-22 at 13:20 +0530, Rahul wrote: > David Nielsen wrote: > > I'd like to mention that the default Evolution setup in FC loads the > > Spamassassin plugin which on my machine at least takes up 80megs of > > memory, replacing that with the bogofilter plugin turned out to be a > > good decision - I blogged a bit about that adventure* > If you think this is a good default solution, would you mind getting > this filed a RFE in Red Hat bugzilla? The evolution maintainer probably > needs to look at this. I will look into it. Spamassassin has infuriated me in the past with its obscene memory consumption. It may be too late for FC6, though.

David Nielsen wrote: > I think we can do this for FC6, it would definitely be worth it, > bogofilter is _much_ faster and doesn't sit there using all your memory > just because you have Evolution open. > > If we get it in before Test3 it should get plenty of testing and we > still have the spamassassin plugin to fallback on if things blow up in > an ugly fasion. Feature freeze is on test 2, not test 3. Playing around with too much changes after test 2 is generally a bad idea.

David Nielsen wrote: > I think we can do this for FC6, it would definitely be worth it, > bogofilter is _much_ faster and doesn't sit there using all your memory > just because you have Evolution open. > > If we get it in before Test3 it should get plenty of testing and we > still have the spamassassin plugin to fallback on if things blow up in > an ugly fasion. Feature freeze is on test 2, not test 3. Playing around with too much changes after test 2 is generally a bad idea.

On Sat, 2006-07-22 at 13:20 +0530, Rahul wrote: > David Nielsen wrote: > > I'd like to mention that the default Evolution setup in FC loads the > > Spamassassin plugin which on my machine at least takes up 80megs of > > memory, replacing that with the bogofilter plugin turned out to be a > > good decision - I blogged a bit about that adventure* > If you think this is a good default solution, would you mind getting > this filed a RFE in Red Hat bugzilla? The evolution maintainer probably > needs to look at this. I will look into it. Spamassassin has infuriated me in the past with its obscene memory consumption. It may be too late for FC6, though.

I'd like to mention that the default Evolution setup in FC loads the Spamassassin plugin which on my machine at least takes up 80megs of memory, replacing that with the bogofilter plugin turned out to be a good decision - I blogged a bit about that adventure* Maybe we can get that plugin upstream as the default for great savings, running a daemon for spam training is probably a tad overkill anyways.

It is optional, it's a plugin look in Edit->Plugins. We just want the default plugin to not suck, you've always been completely free to disable it - we're not Microsoft you know :)