Bug 283211

Summary:	start only those resources which are necessary
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Stefan Majewsky <majewsky>
Component:	server	Assignee:	kdepim bugs <kdepim-bugs>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	andysem, jlayt, oliver.henshaw, sebsauer, stuffcorpse, toddrme2178
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Stefan Majewsky 2011-10-02 22:40:11 UTC

Version:           unspecified (using KDE 4.7.1) 
OS:                Linux

I don't use Akonadi that often. The only application which really uses it at the moment is KMail, but that's only one of two computers. Still, when I log in, the Akonadi server is started because the calendar applet in the clock applet wants to read my calendar. (I know that this can be deactivated, but I'm talking about the default behavior. And of course it's sane to expose this feature by default.)

The situation is: One application wants to read one specific kind of data (calendar events), and Akonadi launches each and every resource within reach. That's a whopping 23 processes on this machine, translating into a whole 100 MB of used memory. A big part of this is the POP3 resources and the maildir resource, so if I don't launch KMail, too, big parts of these resources are down the drain for no good reason.

As you see, both the startup time and combined memory consumption of Akonadi-enabled applications and (through the clock applet) the workspace as a whole can be improved by letting the akonadiserver start only these resources which are relevant for the data to be requested.

I do not know whether such an extension to the Akonadi protocol is possible or feasible. From the outsider's view, it should suffice if both applications and resources could advertise the type of content they're dealing with. I really hope it's simple as that.

Reproducible: Didn't try



Expected Results:

Comment 1 Stefan Majewsky 2011-10-02 22:51:51 UTC

Bug 283212 goes in a similar direction, but I consider it a separate problem and therefore opened it as a separate bug.

Comment 2 Christophe Marin 2012-02-03 15:35:29 UTC

*** Bug 292184 has been marked as a duplicate of this bug. ***

Comment 3 John Layt 2012-05-28 19:56:54 UTC

As I've suggested in the other bug, it would be good if the Plasma Calendar could read an Akonadi config file to see if any Calendar Resources are configured.  If none are configured then there is no point in the calendar asking Akonadi to start.  Is there an easy way to find this out, or can we add a special config file?

Comment 4 Justin Zobel 2021-03-09 05:46:53 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.