1. 28 Jun, 2017 1 commit
  2. 26 Jun, 2017 1 commit
  3. 22 Jun, 2017 5 commits
  4. 21 Jun, 2017 1 commit
    • Daniel Vrátil's avatar
      CollectionStatistics: prefetch all stats on start · de7eea95
      Daniel Vrátil authored
      When Akonadi is started each application and agent starts requesting
      its Collections and statistics. This causes the CollectionStatistics
      cache to query the stats for each Collection individually with the
      very expensive query. On my system all the statistics queries together
      take over 17 seconds.
      
      With this change the CollectionStatistics cache simply pre-fetches
      statistics for all Collections in single a query, which is MUCH
      faster (less than a second on my system), because the expensive JOINs
      only have to be done once.
      
      As a result of this change applications and agents become responsive
      much faster after start and CPU and IO load during start is massively
      decreased.
      de7eea95
  5. 19 Jun, 2017 1 commit
  6. 15 Jun, 2017 1 commit
  7. 11 Jun, 2017 1 commit
  8. 05 Jun, 2017 1 commit
  9. 04 Jun, 2017 1 commit
  10. 01 Jun, 2017 1 commit
  11. 30 May, 2017 1 commit
  12. 29 May, 2017 1 commit
  13. 28 May, 2017 1 commit
  14. 20 May, 2017 2 commits
  15. 15 May, 2017 1 commit
  16. 11 May, 2017 2 commits
  17. 09 May, 2017 2 commits
  18. 06 May, 2017 2 commits
  19. 05 May, 2017 3 commits
  20. 04 May, 2017 1 commit
  21. 03 May, 2017 7 commits
  22. 02 May, 2017 1 commit
  23. 30 Apr, 2017 1 commit
    • Martin Koller's avatar
      don't CreateItem when it is already in the DB. Use ModifyItem instead. · 0c0c2824
      Martin Koller authored
      To avoid running into the "multiple merge candiate" problem when
      akonadi searches items by RID and for whatever reason there are
      really duplicate RIDs, instead when we already have an item ID from
      the DB, avoid using a Create job at all and answer a fetch with
      a Modify Job. Akonadi will then query this item by the given id,
      which is unique and we can never get multiple items in return.
      Also a query by id is faster since it's indexed.
      
      Differential Revision: https://phabricator.kde.org/D5652
      0c0c2824
  24. 29 Apr, 2017 1 commit