Version: unspecified OS: Linux I actually wonder why nobody requested this before, but a search turned up nothing, so... Please disable the Nepomuk Feeder Agents when Nepomuk is disabled. Bonus points for activating and deactivating them in the moment when I activate or deactivate Nepomuk in its KCM. According to <irony>the arguably most precise memory benchmark in the free world (ksysguard)</irony>, this simple change could save at least 22 MB of RAM on my system when Akonadi is active. Reproducible: Didn't try Expected Results:
I suppose the agents could not set up change monitoring when Nepomuk is not running, do a full re-check/re-indexing when the service comes up and stop monitoring again when it is stopped. IMHO quite some additional complexity for encouraging the move of 22MB memory usage from RAM to swap.
*** Bug 285391 has been marked as a duplicate of this bug. ***
My bug got dupe to here, so I am guessing that by disabling the feeders when nepomuk is disabled, it would also disable the barrage of notification popups that result from nepomuk being disabled?
Note: in kdepim 4.8, there's only one feeder (so there's at most one notification for all the plugins (email, calendar, contact) + the optional tag resource which is not installed by default. (and according to <irony>the arguably most precise memory benchmark in the free world (ksysguard)</irony>, it's using a bit less than 8MB here)
@ Christophe: In 4.7.2, I receive a rapid succession of 3 notifications. You're saying the behavior has changed or been fixed in 4.8? Seeing only one notification would be far less disconcerting.
Yes, the behaviour (and the code) changed. In 4.7, the Nepomuk Feeders are 3 distinct resources (hence the 3 notifications) while in 4.8, there's only one akonadi_nepomuk_feeder process (and only one notification).
*** Bug 285999 has been marked as a duplicate of this bug. ***
There is a config option to disable the feeder explicitly which should cover the 22 megs ;-)
An extra configuration option seems like sweeping the issue under the carpet. Honest questions since I don't know the answer. What use do the feeder agents have with nepomuk disabled? What the utility in requiring two config options to fully turn 'nepomuk' off, rather than one?
The extra configuration is there so you can disable the feeder while leaving the rest of nepomuk running. Entirely disabling nepomuk also stops the feeder.
OK. Thanks for the clarification.