Hi,
we're in process of migrating from RC v0.4.2 to v0.5.3 and we've noticed a significant change in caching behaviour.
Ib v0.4.2 Roundcube cached headers for messages that were requested by the user, either single messages or messages that appeared in the mailbox view. So if I had page size set to 40, the first time I login Roundcube would cache 40 message headers.
Roundcube 0.5.3 caches the whole inbox. We have around 200,000 email customers, that's hundreds of millions messages and storing that in DB is pretty pointless.
I'm wondering, what is the reason behind changing the caching behaviour so drastically. Is it configurable? Does it improve searching, navigation performance or something else?
Thanks,
Vlad _______________________________________________ List info: http://lists.roundcube.net/dev/ BT/aba52c80
On 12.07.2011 13:40, Vladimir Minakov wrote:
Roundcube 0.5.3 caches the whole inbox. We have around 200,000 email customers, that's hundreds of millions messages and storing that in DB is pretty pointless.
I'm wondering, what is the reason behind changing the caching behaviour so drastically. Is it configurable?
No it isn't. The change was needed because the cache is-in-sync check was always false before. Now it works. However, we plan to redesign the caching soon, to fix this issue too, maybe in 0.6.
More precissely we'll implement QRESYNC support. Also I think we'll remove messages.idx column and store messages index in cache table. There's also a place for other (performance) improvements.
-
A.L.E.C -
Vladimir Minakov