http://activitystrea.ms/schema/1.0/notetag:social.mxchange.org,2015-01-19:noticeId=85742:objectType=noteNew note by rolandIn case you have #<span class="tag"><a href="https://social.mxchange.org/tag/innodb" rel="tag">InnoDB</a></span> performance problems: Set innodb_locks_unsafe_for_binlog=ON Reason: For UPDATE or DELETE statements, InnoDB holds locks only for rows that it updates or deletes. Record locks for nonmatching rows are released after MySQL has evaluated the WHERE condition. This greatly reduces the probability of deadlocks, but they can still happen. #<span class="tag"><a href="https://social.mxchange.org/tag/mysql" rel="tag">MySQL</a></span> <a href="http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#sysvar_innodb_locks_unsafe_for_binlog" title="http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#sysvar_innodb_locks_unsafe_for_binlog" class="attachment" id="attachment-26298" rel="nofollow external">http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#sysvar_innodb_locks_unsafe_for_binlog</a>http://activitystrea.ms/schema/1.0/post2015-01-19T21:19:53+00:002015-01-19T21:19:53+00:00http://activitystrea.ms/schema/1.0/personhttps://social.mxchange.org/user/1rolandPassionate PHP/Java SE/EE developer and admin of https://social.mxchange.orgrolandRoland HäderPassionate PHP/Java SE/EE developer and admin of https://social.mxchange.orgKrefeld, Germanyhomepagehttp://mxchange.orgtruetag:social.mxchange.org,2015-01-19:noticeId=85742:objectType=thread:crc32=ae6c00ae