Re: MySQL 5.7 Innodb performans issue

2015-05-21 Thread Jørn Dahl-Stamnes
Found the cause. sync_binlog was set to 1. I suspect that the default value is 5.5 was 0 and that is has changed to 1 sometime after that. Setting it to 0 boosted the performance back to normal (4x speed) and the HD LED indicated much lower stress on the hard disk. Found this after I found

Re: MySQL 5.7 Innodb performans issue

2015-05-21 Thread Morgan Tocker
Hi Jørn, Found this after I found out what caused it: https://www.percona.com/blog/2009/01/21/beware-ext3-and-sync-binlog-do-not-play-well-together/ I suspect that this also apply to ext4, or? I would go more specific and say that sync_binlog=1 does not play well with single-threaded

MySQL 5.7 Innodb performans issue

2015-05-20 Thread Jørn Dahl-Stamnes
Hello (again I must say). Over a year ago I experienced a severe drop in the MySQL Innodb performance after ugrading to MySQL 5.6. I did not found any solution to that so I downgraded back to 5.5.33 and lived with in until recently. After a system disk crash I replaced the system disk with

Re: MySQL 5.7 Innodb performans issue

2015-05-20 Thread wagnerbianchi.com
Can you share the SHOW ENGINE INNODB STATUS\G ? -- *Wagner Bianchi, +55.31.8654.9510* Oracle ACE Director https://apex.oracle.com/pls/otn/f?p=19297:4:105567988301604::NO:4:P4_ID:4541, MySQL Certified Professional Percona MySQL Forum http://www.percona.com/forums/ Community V.I.P. Email:

Re: MySQL 5.7 Innodb performans issue

2015-05-20 Thread Jørn Dahl-Stamnes
On Wednesday, May 20, 2015, wagnerbianchi.com wrote: Can you share the SHOW ENGINE INNODB STATUS\G ? Sure, here it is. *** 1. row *** Type: InnoDB Name: Status: = 2015-05-20 20:29:56 0x7f9a4c189700 INNODB

Re: MySQL 5.7 Innodb performans issue

2015-05-20 Thread Morgan Tocker
Hi Jørn, - The data collector system processing jobs, is it multi threaded? Sorry, forgot about that. No, it is not multi threaded. It is a PHP bases system using several script running sequently in an infinite loop. Each script taking care of part of the job of processing the data.

Re: MySQL 5.7 Innodb performans issue

2015-05-20 Thread Jørn Dahl-Stamnes
On Wednesday, May 20, 2015, Morgan Tocker wrote: Hi Jørn, Wagner’s point about SHOW ENGINE INNODB STATUS is a good one. A couple of other questions about your workload: - The data collector system processing jobs, is it multi threaded? Sorry, forgot about that. No, it is not multi

Re: MySQL 5.7 Innodb performans issue

2015-05-20 Thread wagnerbianchi.com
I'd like to add to the Morgan's note that if you want to restrict the number of transactions inside InnoDB kernel to 16, you need at least configure the tickets... = http://www.pythian.com/blog/once-again-about-innodb-concurrency-tickets/ BTW, leave it as its default, IMHO,

Re: MySQL 5.7 Innodb performans issue

2015-05-20 Thread wagnerbianchi.com
Additionally, take a look on this http://wagnerbianchi.com/blog/?p=982 as you're running mysql on SSD -- *Wagner Bianchi, +55.31.8654.9510* Oracle ACE Director https://apex.oracle.com/pls/otn/f?p=19297:4:105567988301604::NO:4:P4_ID:4541, MySQL Certified Professional Percona MySQL Forum

Re: MySQL 5.7 Innodb performans issue

2015-05-20 Thread Morgan Tocker
Hi Jørn, Wagner’s point about SHOW ENGINE INNODB STATUS is a good one. A couple of other questions about your workload: - The data collector system processing jobs, is it multi threaded? - Do you have a sample schema + set of queries we could look at? (We pay close attention to regressions.)

Re: MySQL 5.7 Innodb performans issue

2015-05-20 Thread Jørn Dahl-Stamnes
On Wednesday, May 20, 2015, wagnerbianchi.com wrote: I'd like to add to the Morgan's note that if you want to restrict the number of transactions inside InnoDB kernel to 16, you need at least configure the tickets... = http://www.pythian.com/blog/once-again-about-innodb-concurrency-tickets/