Re: [Evolution-hackers] Memory usage of CamelFolderSummary and CamelImapFolder

[Joe Shaw <joeshaw novell com>]

Hi,

On Thu, 2006-11-16 at 16:13 +0100, Philip Van Hoof wrote:
>   o. The CamelFolderSummary uses mmap. This significantly reduces memory
>      usage because an mmap is on-demand paged.

Does the on-disk format of the CamelFolderSummary change much or at all?
In reading a summary from disk with Beagle, the main problem we've found
is that it is entirely unsearchable, because records within the file are
of variable length and there is no end-of-record marker, which means
that you can't open the file, seek to some random location, and expect
to find where the next (or previous) message begins.  This means that
any time the summary changes, we have to walk the whole thing over again
to see changes.

There was some work a while back to do a "metasummary", which was
essentially a summary of the summary for easier searching, but I'm not
sure what the end result of that was, or if it's in 2.8 or newer.

Joe