Re: SQL errors with large inboxes
Thomas Bruederli <roundcube <at> gmail.com>
2005-11-01 07:36:54 GMT
As mentioned once before and on the road map: We know that the caching
mechanism does not work well with large mailboxes and often reaches the
max_allowed_packet and we're working on it.
To cache also complete message sources has one reason: the parser which
splits messages into different parts needs the whole message body to
work with. Therefore, we put the whole message into the cache (will be
deleted when session ends). The advantage of this behavior are shorter
loading times for attached files, i.e. images that are displayed right
under the text. If the IMAP server is on the same machine or on the LAN,
caching can be disabled but if you connect to remote servers, it can be
The solution would be to split the folder cache into several records or
to have one record per message in the database. We have to make some
speed tests in order to choose one of these solutions.
Please be patient!
Rob Smith wrote:
> The source of his problem was the same as my mysql errors when I
> first started using RC. RoundCube caches the attachments from emails,
> which easily surpasses mysql's default max packet size.
> This ties in with the other emails that have been going around about
> RoundCube's caching. I don't care what database the cache is being
> stored in, I figure mysql works fine, but if files are faster, I guess
> we can do it that way. More importantly, why are we caching
> attachments? They are large, and usually only downloaded once by the