Coming back to my original message, here is the current status and the
“fix”.
As part of my configuration I have a number of smart mailboxes (e.g, A1)
that I use to identify sets of messages. Next I have a number of other
smart mailboxes that include in their conditions the use of the test
(“is not in” A1).
Benny says it’s the use of “is not in” that’s the issue. It
manifests a “performance bug”. At least part of the issue is that
MailMate is not particularly efficient about making that calculation.
If I allow myself to be patient the “spinning beachball” does
eventually complete, mostly in around 10-15 minutes but I have waited
over an hour.
Benny’s pretty sure there’s something else going on too. The
primary point here is that this will not be an easy fix.
The fix I have is really a work around. Step 1, don’t use “is not
in”.
Step 2, in the smart mailboxes I use to identify sets of messages, I
added a rule to set a mailbox unique tag to messages in those mailboxes,
e.g., the name of the mailbox A1. Then, in the mailboxes where I
don’t want those messages to appear, I use the condition “Tags is
not A1”.
Works like a charm. No more “spinning beachball of death”. I am
once again a very happy MailMate user.
Benny is going to continue to study the issue and hopefully identify a
way to be more efficient about calculating “is not in”.
Thanks to all, especially Benny,
Jim
On 10 Jan 2018, at 9:42, James Galvin wrote:
Well, I have finally reached my breaking point. Here’s hoping
someone can help.
In the past 60 minutes (and yes I mean 60 minutes) I have “FORCE
QUIT” MailMate more than 10 times because it got to the “spinning
beachball of death”.
I’ve caught up on all the threads over the past year or so regarding
performance, slowness after upgrading to High Sierra, and the spinning
pizza.
I even caught Benny’s two suggestions related to all that:
1. delete “everything” in your database and resync MailMate
2. execute the following: sample MailMate 10 -f
~/Desktop/sample_mailmate.txt
Bad behavior:
I don’t know exactly when it started but I do know it happened prior
to my High Sierra upgrade.
MailMate arbitrarily finds itself in the “spinning beachball of
death”. There is no pattern. It is random as far as I can tell.
It can happen at any moment and after executing any command. It
happens 3-8 times a day for me and has been for some time.
One thing that has been getting worse that might be useful is that
deleting messages (doesn’t matter the quantity) starting taking 20
seconds or more. Yes, whenever I hit DELETE MailMate goes to the
spinning beachball for at least 20 seconds. Since I rarely delete
messages this hasn’t been a real problem.
Today, for the first time, I opened my laptop and MailMate immediately
went to the “spinning beachball of death”. This is the first time
I remember it doing this without having executed a command first.
Over the recent holiday I completely deleted my entire MailMate
database, as recommended in a prior thread on this list by Benny, and
resynced everything. I enjoyed about 5 days of blissful email before
MailMate went rogue.
What’s next:
I have collected 6 samples as previously suggested in other threads
from MailMate over the past 2 days, all when it is in “spinning
beachball of death” mode just prior to my “FORCE QUIT”. I will
send those to Benny immediately following this message privately.
This is my environment:
MailMate
Version 1.10 (5443)
MacBook Pro (Retina, 13-inch, Late 2012)
Processor 2.5 GHz Intel Core i5
Memory 8 GB 1600 MHz DDR3
I sure do hope I can get past this.
Thanks!
Jim
_______________________________________________
mailmate mailing list
mailmate@lists.freron.com
https://lists.freron.com/listinfo/mailmate
