[mew-int 01753] Re: Mew-4.x VERY slow

[Kazu Yamamoto ( 山本和彦 )]

Hello,

From: George Kahler <george at example.com>
Subject: [mew-int 01748] Mew-4.x VERY slow

> A folder with 4,500 messages to re-scan takes mew-v3.3 about 
> 1 min and 44 sec.
> 
> The same folder, after deleting mew-3.3 and installing mew-4.062,
> takes about 4 min and 47 sec to re-scan.
> 
> Needles to say that any activity that causes to scan a folder is
> horrendously slow.
> 
> Is this a known problem ? Kazu, can you pls look into it ?

I think you are talking about scanning a local folder (not a remote
folder).

For Mew 3, 'mewls' displays a header and sleep (to give CPU time to
Mew), and repeats this. This seems a very ad-hoc way to me.

Mew 4 synchronizes 'mewl'. 'mewl' dispalys a header and wait for the
'\n' character from Mew. I believe this is the best way to support
Emacs/XEmacs/Meadow. (Timing differs among Emacses, sigh.)

Moreover, since Mew 4 displays bodies of messages, additional cost was
added.

If you are using Meadow on Windows, set w32-pipe-read-delay to some
between 0 and 50. Its default value is 50. Because we cannot bind this
as a local variable, Mew does not change the value. If your value is
too small, problems would occurs. I heard ange-ftp does not work with
the value 0.

> BTW, other colleagues, here, are experiencing the same problem. Theirs on
> Linux, my on Solaris.

Uhhmmm. If Mew is too slow on *UNIX*, we need to investigate the code
to find a bottle neck.

--Kazu