Pages: 1
RSS
Disk churning, Disk is churning continuously
 
I installed The Bat! version 5.0.14 on Microsoft Windows XP Pro SP3.  When the program is running, the disk is churning continuously.  I have no idea what it could be doing.  It is unusable.
 
get Process Monitor and see what's doing that. Could be something else. Or if it is theBat, you'll see what it tries to do.
Or just install some previous version. Acc. to my long time experience with theBat, new major versions become stable near the end of their life cycle :0, so last 4.x is a good choice.
I still use v 3.85 for work and test later versions only with accounts I don't care about.
 
Quote
bigg one wrote:
Acc. to my long time experience with theBat, new major versions become stable near the end of their life cycle :0, so last 4.x is a good choice.



That was clinical and cold (but seems like quite accurate)!!!!!
 
Thanks for the tip.  There's not much chance to run any kind of monitors.  The Bat! consumes all CPU and disk time.
 
Could you give us some more details on your setup? All CPU and disk time seems a bit excessive.
Over here TB uses 32 MB RAM and no CPU-time, that's with six accounts (4 pop3, 2 imap) and a messagebase of more than 120,000 messages in 100+ folders. And also 100+ filters. I'm running an AV plug-in, but no spam plug-in, spm filtering is done on my server.
According to the beta list virtual folders are a real resources hog, but I can't comment on that as I don't use those.
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
 
An image can be found below.

http://cogit.net/images/bat110627.png

The CPU usage is reasonable, but the disk usage is so high that I run The Bat! only under duress.  I do have virtual folders.
Edited: mikeyww - 27 June 2011 18:26:07
 
Apart from virtual folders, how many account, messages, etc
What plug-ins are you using?
What hsappens when you disable or delete the virtual folders....
__________________________________
I'm just a user of The Bat! I don't work for Ritlabs.
 
When I disabled auto-refresh on the virtual folders, the problem disappeared.  Thanks for the suggestion.
Pages: 1