[
https://issues.apache.org/jira/browse/JAMES-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier updated JAMES-3408:
----------------------------------
Attachment: 94106692-2212d400-fe66-11ea-96bd-2c43d7fefc8a.png
> IMAP LIST should not query "mailbox counters"
> ---------------------------------------------
>
> Key: JAMES-3408
> URL: https://issues.apache.org/jira/browse/JAMES-3408
> Project: James Server
> Issue Type: Improvement
> Components: IMAPServer, mailbox
> Reporter: Benoit Tellier
> Priority: Major
> Attachments: 94106692-2212d400-fe66-11ea-96bd-2c43d7fefc8a.png
>
>
> This information is unused.
> Remove "mailbox counters" from `MailboxManager::search` MailboxMetdata POJO.
> JMAP-draft and JMAP-RFC8621 will need to rely on a brand new
> `mailboxManager.getMailboxCounters(ids)` calls as part of `Mailbox/get`.
> This is even more important to avoid paying the price of mailbox-counters
> read repairs upon IMAP LIST.
> = Definition of done
> Using glowroot on DEV (or locally on a distributed-james server), access your
> mailbox via IMAP and Thunderbird.
> Go in the IMAP LIST transaction, there should be no "mailbox counters" calls.
> = Diagnostic
> While looking at the Glowroot board:
> {code:java}
> Transaction type: IMAP
> Transaction name: IMAP processor :
> org.apache.james.imap.processor.ListProcessor
> Start: 2020-06-29 5:04:15.319 am (+07:00)
> Duration: 29,310.3 milliseconds
> {code}
> We saw that we have some IMAP list slow traces, mostly due to the (very) high
> count of mailboxes... (104)
> A closer look at executed queries shows around a third of the query time is
> spent retrieving mailbox counters. Which is not part of the IMAP list
> response.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
