-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, March 20, 2006 10:12, eCet wrote:
>> I agree with this last statement. The backend has a _lot_ to do with
>> this issue. We use an NFS appliance for a backend that we were
>> experiencing problems with (high latency) that caused the same issue
>> with large mailboxen.
>
> So if i'm understand right: You are working on this issue?
>> After correction I can open a maildir mailbox with
>> 40,000+ messages successfully (after about 2 minutes).
> The opening is not an issue in this 20Kbox it opens (and sorts)in about
> 20secs to 2min.
> Threading is another question it took 5-6mins.
That would be because just doing a normal sort/display doesn't involve any
work on the part of SquirrelMail to be honest. Threading is something
entirely different. Threading returns a formatted string of message ids
that then needs to be processed and the message information from the
server. This is two seperate IMAP calls. The first returns data that
looks like this:
(1 (2 3 4)) (5) (6 (7 (8 9)))
This basically creates a thread that looks like this:
+ 1
- 2
- 3
- 4
+ 5
+ 6
+ 7
- 8
- 9
These IDs then need to be passed onto the code that fetches the message
information. This list of IDs is potentially enormous, especially in
folders that have 20k messages (that's 20k message IDs that need to be
returned).
The second step in this function is the same used when issuing a fetch
from just a sorted list. The list of message IDs is passed to a function,
which then simply fetches a select number of messages (start message
through to the number of messages a user has displayed).
Basically summarized, you'll probably find the hangup is in processing the
results from the THREAD call. The only way we could probably reduce the
processing time is to cut down the results by issuing a search criteria to
the THREAD command. Unfortunately that's close to impossible as it'd
probably make it impossible to go back a certain date range, or we'd have
to start doing time calculations and display results from date a to date
b, and when you get close to date b, extend the search to be from date b
to date c.
>> Using Courier, server-side sorting, SM 1.4.5. Make sure your disks, etc
>> are fast and aren't experiencing high IO load and are optimized for
>> reading.
> My discs are quite fine, and I use jfs. Of course there is a bit IO load
> every time, it is a server machine. I will look some tweaks in fs.
> Understand so. So I think I will disable server-side threading, the
> Thread view button disappears so (users can't thread view). And I will
> give a custom memory limit to php scripts, that users can't do anything
> nasty with such big mailboxes. I have to let server side sorting in SM, to
> help quick open the mailboxes. Oh, the whole thing is not an issue with
> imap mailer client like ThunderBird(I know, that it is another think).
Probably because Thunderbird is doing it client side, ie fetching the
information needed to do the threading from the messages, rather than
getting the information about the threads from the IMAP server itself.
- --
Jonathan Angliss
<[EMAIL PROTECTED]>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iEYEARECAAYFAkQe4AoACgkQK4PoFPj9H3NuYgCfSHgfbvOKPTvnlwGHeBmtYEEb
h2YAoIT3mRzs+Zeote9rZBy2ncRQ2Syw
=uNA2
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
--
squirrelmail-users mailing list
Posting Guidelines:
http://www.squirrelmail.org/wiki/MailingListPostingGuidelines
List Address: squirrelmail-users@lists.sourceforge.net
List Archives:
http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id)95
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
