Akonadi database performance

[Till Adam]

On Tuesday 22 February 2011 16:06:18 Volker Krause wrote:
> Hi,
> 
> On Tuesday 22 February 2011 15:06:59 Bjoern Ricks wrote:
> > on the kde-mobile-user maillinglist we got feedback about unpleasant
> > performance of akonadi on Maemo5 (N900) with large account (>=1GB).
> 
> bad performance during syncing or accessing data?
> 
> > We at
> > Intevation thought about how to improve the database (in this case
> > sqlite) and as a first step it would be nice to integrate the database
> > index change from
> > http://quickgit.kde.org/?p=akonadi.git&a=commit&h=8a2400f131cba56c6c8ce3
> > 7e27 073c23210d7fb2 for all mobile plattforms. The database indexes
> > aren't necessary and can be dropped. Maybe it would also good to
> > integrate the patch for
> > desktop builds. We have seen big improvements of the inital sync
> > duration. It was approximately 40% faster then before on wince.
> 
> It's not that easy I'm afraid. All those indexes were added because either
> common read operations or Akonadi startup were way too slow with large
> amounts of data. Of course indices have a negative impact on write
> performance, but that's usually the less common case.
> 
> > In general the performance improvements in akonadi are not easy to
> > quantify. Sometimes it's not more then a feeling. It would be nice to
> > implement some benchmarks based on real akonadi workflows and
> > afterwards try to improve several aspekts.
> 
> kdepimlibs/akonadi/tests has benchmarks for common item/collection
> operations.

It's also likely that these indeces were added in MySQL times. So it remais to 
be assessed to which extent they impact performance relative to the backend 
and usage pattern.

Till