Patrick Nagel wrote:
I made some changes (please check that I didn't change the meaning, Alec) and formatted it for the TRAC Wiki. I think 'Howto_Performance_tuning' would be a good page name. Unfortunately I seem to not have enough rights to create a Wiki page (that's a weird policy, if you ask me... it's a Wiki!). The Wiki told me so on pressing the 'save' button...
Currently I have no rights to create a page too. I'm sure it was possible before... In the mean time, thanks for your correction there's only one misunderstanding.
"The caching is not always faster though, and cache update operations are expensive."
This is not exactly what I'd like to say about the cache update process. Roundcube is always making a check of cache completeness. In general, it compares messages counts in the server and in the cache, it also checks UIDs of some (most recent) messages. If something differs the cache is assumed dirty and is updated (fetching headers of messages for current list page from IMAP server). Let's suppose a folder with 1k of messages. Not every message have been viewed or listed by Roundcube, so cache contains, let's say, a hundred. In this simple and common case the cache will be always dirty until you will list each message. This probably should be fixed in future versions, but that's how it works.
Also we could add:
=== 'imap_root', 'imap_delimiter' ===
If you know your imap's root directory and its folder delimiter, you can specify them here. This will save one NAMESPACE and one LIST call.