Bug 757416

I wonder whether those wakeups are really Akonadi's fault and not MySQL's…

That could be but since akonadi is what brings mysqld in it's the one that gets the blame.

For comparision, powertop reports akonadi/sqlite not  even in the top 20 for wakeups, akonadi/mysql was 8 with:

609.1 µs/s      10.9        Process        /usr/libexec/mysqld --defaults-file=/home/rdieter1/.local/share/akonadi//mysql.conf --

ie, approx 10.9 wakeups/second

So, if you value resource usage and wakeups (over performance), I'd suggest you trying switching akonadi to use a sqlite backend instead:

systemsettings->akonadi configuration->akonadi server configuration(tab)

and click 'restart akonadi' button


Another item to consider is to disable nepomuk strigi indexing (at the cost of reduced functionality when/if doing searches on email):
systemsettings->desktop search->basic settings(tab)
*uncheck* 'enable strigi desktop file indexer'

(In reply to comment #3)
> For comparision, powertop reports akonadi/sqlite not  even in the top 20 for
> wakeups, akonadi/mysql was 8 with:
> 
> 609.1 µs/s      10.9        Process        /usr/libexec/mysqld
> --defaults-file=/home/rdieter1/.local/share/akonadi//mysql.conf --
> 
> ie, approx 10.9 wakeups/second
> 
> So, if you value resource usage and wakeups (over performance), I'd suggest you

No I can't say I am willing to take even bigger performance hit as at the moment Kmail2 is not really usable for me (compared to Kmail1 that I had with F15).

> trying switching akonadi to use a sqlite backend instead:

Also, don't akonadi guys advise against using sqlite backend in their FAQ?

> 
> systemsettings->akonadi configuration->akonadi server configuration(tab)
> 
> and click 'restart akonadi' button
> 
> 
> Another item to consider is to disable nepomuk strigi indexing (at the cost of
> reduced functionality when/if doing searches on email):
> systemsettings->desktop search->basic settings(tab)
> *uncheck* 'enable strigi desktop file indexer'

That's been turned off since the original install of F11 (or 10? I don't recall). As I mentioned I do not really use indexing, I generally know where stuff is and otherwise grep is always there for me.

So I see:

 3188 dtor      20   0  755m 120m  15m R 87.4  3.1 328:01.71 akonadi_nepomuk                                                  

That's tad too much, don't you think?

Thanks.

> Also, don't akonadi guys advise against using sqlite backend in their FAQ?

Yes, they do. That's why it's not the default.

In fairness, the advice is based mostly for performance reasons.  It's not that sqlite is *bad* per-se, I mean it is the default used on some other platforms, like meego (and friends).

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.