Re: WARNING: sometimes two copies of mysqld are running after stopping and starting Akonadi

Am Mittwoch, 28. Januar 2015, 11:21:49 schrieb René J.V. Bertin:
> On Wednesday January 28 2015 10:38:10 Martin Steigerwald wrote:
> >I read quite some times that people do
> >
> >akonadictl restart
> >
> >to work around and fix up issues with Akonadi temporily.
> >
> >I recommend: Don´t.
> 
> I do this regularly and never had issues, not even on a slow machine, on
> Linux and on OS X.
> 
> It would be interesting to know which mysql server people use who run
> into this issue. I replaced the default one shipped by Ubuntu with the
> MariaDB server, configured to use InnoDB through
> ~/.local/share/akonadi/mysql.conf. Extracts from that file:
> 
> # init file that disables logging:
> init_file=/home/bertin/.config/mysql-no-logging.sql
> # for running on ZFS:
> innodb_use_native_aio=0
> innodb_doublewrite = 0
> # use InnoDB for transactions and better crash recovery
> default_storage_engine=innodb
> innodb_buffer_pool_size=256M
> innodb_log_buffer_size=10M
> query_cache_size=64M

mysql-server-core 5.5.40-1 on Debian.

I had a go at MariaDB, but

martin@merkaba:~> apt-cache show akonadi-backend-mysql | grep Depends
Depends: libqt4-sql-mysql, mysql-server-core-5.5 | mysql-server-core

(reported a bug with Debian about it quite some time ago.)

Well that said, with my self-compiled Akonadi 1.13 branch git I suppose I 
can easily use MariaDB. But I do not want to deviate from distro setup 
more than absolutely needed.


martin@merkaba:~/.local/share/akonadi#1> bzr diff -r 115..124 mysql.conf
=== modified file '.local/share/akonadi/mysql.conf'
--- .local/share/akonadi/mysql.conf     2014-06-11 20:08:58 +0000
+++ .local/share/akonadi/mysql.conf     2015-01-23 08:20:57 +0000
@@ -39,11 +39,11 @@
 
 # memory pool InnoDB uses to store data dictionary information and other 
internal data structures (default:1M)
 # Deprecated in MySQL >= 5.6.3
-innodb_additional_mem_pool_size=1M
+innodb_additional_mem_pool_size=16M
 
 # memory buffer InnoDB uses to cache data and indexes of its tables 
(default:128M)
 # Larger values means less I/O
-innodb_buffer_pool_size=80M
+innodb_buffer_pool_size=512M
 
 # Create a .ibd file for each table (default:0)
 innodb_file_per_table=1
@@ -53,7 +53,7 @@
 
 # Buffer size used to write to the log files on disk (default:1M for 
builtin, 8M for plugin)
 # larger values means less I/O
-innodb_log_buffer_size=1M
+innodb_log_buffer_size=16M
 
 # Size of each log file in a log group (default:5M) larger means less I/O 
but more time for recovery.
 innodb_log_file_size=64M



Hmmm, I wonder why I raised innodb_additional_mem_pool_size=16M I think I 
will lower it to the default again.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users