periodic slowness

[Kevin Baker]

hi,

I've been using mutt-kz for quite a while now. In the last couple of
days the command input seizes for about a second before completing the
command. For example if I'm in my INBOX and I hold down the 'j' key it
will zip along and then seize for a second before continuing. Happens
about every 200-300 messages. Quite annoying! ;-)

I'm on F18 and yum updated a few times in the last week so it may be
related to that. I uninstalled mutt-kz and reverted to the F18 mutt and
confirmed that it does not have the same behaviour - works fine.

Anyone else seen something like this?

thanks

Kev

[Kevin Baker]

problem solved.

I spent some time today trying to isolate the problem. I found that
there is one folder in my mailboxes menu that, when removed, stops the
seizing behaviour. The only difference I can see is that all the other
folders are <folder-name>/{cur,new,tmp} and this one is just a single
file - and it's large - around 220M. So my guess is that the menu is
periodically scanning the folders to update the count of emails. The
former structure is probably just a directory scan and the latter would
be a file open and parsing the contents.

Kev

On Thu, Jul 11, 2013 at 10:59:18AM -0400, Kevin Baker wrote:
> hi,
>
> I've been using mutt-kz for quite a while now. In the last couple of
> days the command input seizes for about a second before completing the
> command. For example if I'm in my INBOX and I hold down the 'j' key it
> will zip along and then seize for a second before continuing. Happens
> about every 200-300 messages. Quite annoying! ;-)
>
> I'm on F18 and yum updated a few times in the last week so it may be
> related to that. I uninstalled mutt-kz and reverted to the F18 mutt and
> confirmed that it does not have the same behaviour - works fine.
>
> Anyone else seen something like this?
>
> thanks
>
> Kev

[sankarshan]

On Fri, Aug 9, 2013 at 11:15 PM, Kevin Baker  wrote:
> I spent some time today trying to isolate the problem. I found that
> there is one folder in my mailboxes menu that, when removed, stops the
> seizing behaviour. The only difference I can see is that all the other
> folders are <folder-name>/{cur,new,tmp} and this one is just a single
> file - and it's large - around 220M. So my guess is that the menu is
> periodically scanning the folders to update the count of emails. The
> former structure is probably just a directory scan and the latter would
> be a file open and parsing the contents.

Possibly. An earlier instance when mainline mutt started doing similar
behaviour, I had to remove a mailbox of a suitably large size (which I
had the misfortune of importing badly).

[David Sterba]

On Fri, Aug 09, 2013 at 01:45:04PM -0400, Kevin Baker wrote:
> problem solved.
>
> I spent some time today trying to isolate the problem. I found that
> there is one folder in my mailboxes menu that, when removed, stops the
> seizing behaviour. The only difference I can see is that all the other
> folders are <folder-name>/{cur,new,tmp} and this one is just a single
> file - and it's large - around 220M. So my guess is that the menu is
> periodically scanning the folders to update the count of emails. The
> former structure is probably just a directory scan and the latter would
> be a file open and parsing the contents.

By 'menu' you mean the sidebar? I've probably observed the same some
time ago and sent a patch to add 'sidebar_refresh' config option to tune
the periodic refresh, that's 60 seconds by default, and 0 turns it off
with the expected result of stale message count.

HTH,
david