Bug 260630 - akonadi uses big mysql log files
Summary: akonadi uses big mysql log files
Status: RESOLVED NOT A BUG
Alias: None
Product: Akonadi
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE RPMs Linux
: NOR normal with 40 votes (vote)
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-18 14:46 UTC by Bernhard M. Wiedemann
Modified: 2014-05-30 07:21 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard M. Wiedemann 2010-12-18 14:46:47 UTC
Version:           unspecified (using KDE 4.5.85) 
OS:                Linux

akonadi comes with a mysql.conf file that has "innodb_log_file_size=64M" 
which means that KDE-LiveCDs will waste 128MB of RAM just for the two logfiles. 
The default log size is 5MB so there should be a very good reason to have it that big.
Additionally, wasting over 100MB per user on disks of regular installs is also not nice.

Reproducible: Always

Steps to Reproduce:
du -m ~/.local/share/akonadi/db_data/ib_logfile*

Actual Results:  
64
64

Expected Results:  
5
5
Comment 1 Christophe Giboudeaux 2010-12-26 23:52:09 UTC
This is for performance reasons. See the following page for the details: http://techbase.kde.org/Projects/PIM/Akonadi#Akonadi_needs_too_much_space_in_my_home_directory.21
Comment 2 Christoph Feck 2010-12-27 02:32:04 UTC
See also bug 217016 for possible workarounds.
Comment 3 Murz 2014-05-30 07:18:59 UTC
Confirm this problem, each user that contains almost empty database, eats 128 MB of logfiles (64mb in ib_logfile0 and 64mb in ib_logfile1)!
I think that size of log files must be smaller, or maybe depend of database size.
Comment 4 Murz 2014-05-30 07:21:12 UTC
At now we can fix this via changing defaults config file /etc/akonadi/mysql-global.conf
- string
innodb_log_file_size=64M
change to
innodb_log_file_size=1M