james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joachim Draeger (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JAMES-720) STATUS command performance
Date Sun, 03 Dec 2006 22:19:23 GMT
    [ http://issues.apache.org/jira/browse/JAMES-720?page=comments#action_12455216 ] 
Joachim Draeger commented on JAMES-720:

I could improve the performance by a  join between message_row and message_flags in TorqueMailbox.getMessages().
BTW Torque is quite limited and sometimes cumbersome doing this.

The cache is not used for optimizing data access but for MSN stability on external access
to the db by a different host. 
Another goal is to deliver appropriate events if Flags are changed externally.
(I realized some ideas I had for cluster use)
There was a reason, I don't remember right now, why I forced to load  the uid cache on startup.
Did you run the tests? 
Of course loading them on first need would be better. But before I don't know, if the reason
still exists, I prefer loading them on init().

> STATUS command performance
> --------------------------
>                 Key: JAMES-720
>                 URL: http://issues.apache.org/jira/browse/JAMES-720
>             Project: James
>          Issue Type: Improvement
>          Components: IMAPServer
>    Affects Versions: Trunk
>         Environment: evolution email client 
>            Reporter: Robert Burrell Donkin
>         Assigned To: Joachim Draeger
>         Attachments: STATUS-perf.patch
> I've been running my server for a little while with extra performance logging to try
to work out why it's sluggish. 
> The command parsing is orders of magnitudes faster than the data access. 
> The reasons seems to be the performance of the STATUS command. Since STATUS is typically
called every couple of minutes for every mail box visible on screen, it's quite a significant
issue for this email client. (some other clients use SEARCH instead but this is no currently
> This performance seems to worsen quickly as the number of messages in the box increases.
> On my box:
> STATUS on an empty mailbox with three empty sub mailboxes takes ~45 ms
> STATUS on a mailbox with ~10 read messages takes ~100ms
> STATUS on a mailbox with ~ 50 messages with 40 unread takes ~450ms
> STATUS on a mailbox with ~ 150 with 40 unread takes ~1800ms
> STATUS on a mailbox with ~ 570 unread messages takes ~6600ms
> Any clues about where to start looking?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message