Adding one domain takes 90 seconds !!!

[Spacedust]

Why this is slow

I'm using high-end dedicated server without any users on it and it's superbly slow !

It was working well on Kloxo 6.5.0 candidate and now it's way too slow.

Script is waiting for something and I cannot figure it out for what...

Fix this Mustafa !

[MRatWork]

I found issue related to Kloxo-MR update. In certain condition, process like change root password not work and reboot solve this issue. It's not related to Kloxo-MR code but mysql/mariadb problem.

[Spacedust]

It's always successful but it takes 90 seconds to add one domain ! Reboot does not help !

[Spacedust]

Tested on clean VirtualBox:

- adding domain on MySQL takes 11 seconds
- adding domain on MariaDB takes 14 seconds

So why my production server needs 90 seconds

[MRatWork]

Have you convert all database tables to innodb using 'sh /script/mysql-convert'?

[Spacedust]

Have you convert all database tables to innodb using 'sh /script/mysql-convert'?

No I still use MyISAM. It was working well on MySQL and older versions of Kloxo.

[Spacedust]

Have you convert all database tables to innodb using 'sh /script/mysql-convert'?

My server.cnf - server is having 32 GB DDR3 + 2x120 GB SSD disk in software RAID1

Code: [Select]

[mysqld]
#skip-networking
#bind-address = 0.0.0.0
#server-id=1
#log-bin = mysql-bin
#skip-name-resolve
#skip-grant-tables
datadir=/var/lib/mysql
tmpdir=/dev/shm
socket=/var/lib/mysql/mysql.sock
user=mysql
#log_warnings=2
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
#skip-federated
old_passwords=1
skip-external-locking
query_cache_limit=64M
query_cache_size=256M
query_cache_type=1
max_connections=1000
max_user_connections=50
max_connect_errors=100
#wait_timeout=180
thread_handling = pool-of-threads
thread_cache_size=8
key_cache_segments=8
key_buffer=3172M
innodb-buffer-pool-instances=8
innodb_buffer_pool_size = 3172M
innodb_thread_concurrency = 8
innodb_log_file_size=64M
innodb_log_buffer_size = 16M
innodb_lock_wait_timeout = 100
innodb_flush_log_at_trx_commit = 2
innodb_support_xa=0
#innodb_additional_mem_pool_size = 32M
innodb_read_io_threads = 8
innodb_write_io_threads = 8
innodb_max_dirty_pages_pct = 90
innodb_file_per_table
innodb_use_native_aio=0
sync_binlog=0
join_buffer_size=4M
max_allowed_packet=32M
table_open_cache=1024
table_cache=32k
sort_buffer_size=4M
read_buffer_size=4M
read_rnd_buffer_size=4M
max_connect_errors=100
tmp_table_size=32M
max_heap_table_size=2M
long_query_time=2
thread_concurrency=8
myisam_sort_buffer_size=64M
max_write_lock_count = 1
default-storage-engine=MyISAM
#collation-server = utf8_unicode_ci
#init-connect='SET NAMES utf8'
#character-set-server = utf8

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
plugin-load=archive=ha_archive.so;blackhole=ha_blackhole.so

[mysqldump]
quick
max_allowed_packet=16M


[MRatWork]

I mean have you run 'sh /script/mysql-convert --engine=innodb'?.

Mix storage-engine inside database tend to slow database access. Mysql55 (from ius) and MariaDB hate or have a problem for myisam.

[Spacedust]

I mean have you run 'sh /script/mysql-convert --engine=innodb'?.

Mix storage-engine inside database tend to slow database access. Mysql55 (from ius) and MariaDB hate or have a problem for myisam.

No I didn't. I just have a few InnoDB databases and a lot of MyISAM.

Can I send you my VPS details ? Just add a domain under admin and you will see what's wrong.

[MRatWork]

I mean have you run 'sh /script/mysql-convert --engine=innodb'?.

Mix storage-engine inside database tend to slow database access. Mysql55 (from ius) and MariaDB hate or have a problem for myisam.

No I didn't. I just have a few InnoDB databases and a lot of MyISAM.

Can I send you my VPS details ? Just add a domain under admin and you will see what's wrong.

Ok, I will try to find out what different thing between your server with my 'standard' server.

[MRatWork]

I found your database mariadb installed on your system but database tables still using myisam storage-engine. It's bad combination.

You must run 'sh /script/mysql-convert --engine=innodb' to convert tables to innodb.

You have 2 options:

1. Use MariaDB or mysql55 and then convert tables to innodb, or
2. downgrade to mysql51 and stay with myisam

[Spacedust]

I mean have you run 'sh /script/mysql-convert --engine=innodb'?.

Mix storage-engine inside database tend to slow database access. Mysql55 (from ius) and MariaDB hate or have a problem for myisam.

No I didn't. I just have a few InnoDB databases and a lot of MyISAM.

Can I send you my VPS details ? Just add a domain under admin and you will see what's wrong.

Ok, I will try to find out what different thing between your server with my 'standard' server.

Mustafa, please install latest Kloxo-MR final on VirtualBox, put some large files on admin and then run /script/scavenge. You will see that Disk Usage won't work. I still don't know why :/