A BUGNOTE has been added to this bug. ====================================================================== http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000139 ====================================================================== Reported By: aaron Assigned To: ====================================================================== Project: DBMail Bug ID: 139 Category: IMAP daemon Reproducibility: always Severity: feature Priority: normal Status: new ====================================================================== Date Submitted: 12-Dec-04 00:27 CET Last Modified: 12-Dec-04 09:34 CET ====================================================================== Summary: dbmail-imapd doesn't scale nicely with large message ranges Description: Thomas Mueller wrote:
Sometimes my server uses for some minutes much more memory than it should - and I guess it's dbmail. I hope I'll find some time soon to use a profiler, but meanwhile I guess the following happens: someone marks a mailbox for offline use and dbmail-imapd does the following: - fetch all mails from database - keep the result set in memory - deliver them The third step can take a while so the process eats lots of memory for quite some time - no bug, its a design problem. This only happens for some minutes, that's why I'm quite sure it's no memory hole. The way to go would be to use a server side cursor so only one mail has to be kept in memory - but AFAIK there's a storage system with SQL interface (sorry couldn't resist) that doesn't support cursors. ====================================================================== ---------------------------------------------------------------------- aaron - 12-Dec-04 00:30 CET ---------------------------------------------------------------------- Paul, you might know this code best, is there someplace in _ic_foo() that goes through a result list from the database and builds some huge thing in memory, and then begins to send it back to the client? It might be as simple as placing some ic_write()'s in the middle of that loop, rather than building up the whole structure at all. ---------------------------------------------------------------------- paul - 12-Dec-04 09:34 CET ---------------------------------------------------------------------- There is basically only one candidate: _ic_fetch Thomas was referring to the use-case where users mark a mailbox for offline usage. This probably triggers something like: C: A001 UID FETCH 1:* (FULL) This will first retrieve the full range of message_idnr with their flags using db_get_msginfo_range, and after that start retrieving the full messages one-by-one and dumping them to the client. There is no place in the code where messageblks for more than one message at a time are selected. There should be, once we can support cursors, but for now dbmail is on a one-message-at-a-time paradigm. So, db_get_msginfo_range will build a large result-set that should scale well since it's holding only the message_idnr and the flags, and afterwards messageblks for these messages are selected, one message at a time. It could be this long loop that retrieves the full messages is 'leaking' memory during its run: rescaling the memory allocated for the cache to the largest message retrieved, and not releasing that memory until the end of the loop. Bug History Date Modified Username Field Change ====================================================================== 12-Dec-04 00:27aaron New Bug 12-Dec-04 00:30aaron Bugnote Added: 0000439 12-Dec-04 09:34paul Bugnote Added: 0000441 ======================================================================
