Bug 169564 - HUGE CPU-load with a large cachedimap mbox
Summary: HUGE CPU-load with a large cachedimap mbox
Status: RESOLVED DUPLICATE of bug 163469
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.9
Platform: unspecified FreeBSD
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-22 02:30 UTC by mi+kde
Modified: 2008-08-22 15:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mi+kde 2008-08-22 02:30:48 UTC
Version:           1.9.9 (using 3.5.9, compiled sources)
Compiler:          Target: amd64-undermydesk-freebsd
OS:                FreeBSD (amd64) release 7.0-STABLE

My INBOX is fairly large (thousands of e-mails, 265Mb total size) and I'm using cachedimap to access it and other mboxes on the same server (total size of all boxes combined is about 780Mb).

I noticed, that kmail tends to consume an entire CPU (I have 4 in this system) for hours, when this account's tree is open.

I could see, how the size of the box could slow down various operations, but there is no reason to chew-up CPU-time while waiting for the server. In fact, Thunderbird, with which I access the same account from another location, has no problems with the size.

I thought, maybe, I'm asking it to re-check the mail too often, but the problem did not go away even after I bumped the refresh interval from 7 to 13 minutes.

Please, advise.
Comment 1 mi+kde 2008-08-22 02:40:35 UTC
Forgot to mention: when this happens, the application is NOT completely unresponsive -- just slow to respond. Once I collapse the account's tree, response time improves significantly and the CPU consumption drops from 100% to about 5% of one of the CPUs (still huge for Opteron-2200, I'd say) and I can brows other accounts' mailboxes comfortably.

But this largest one is nearly unusable...

The process is a 64-bit one, and my computer has 4Gb of RAM.
Comment 2 Thomas McGuire 2008-08-22 15:33:33 UTC

*** This bug has been marked as a duplicate of bug 163469 ***