Hello all,<br /><br /><br />have used Sysbench extensively to test MariaDB CPU
load factors between various architectures.<br /><br />I am noticing massive
amounts of &quot;[ERROR] mysqld: Deadlock found when trying to get lock; try
restarting transaction&quot; in the MariaDB error log during the R/W phase. The
Sysbench R/W TPS rates are still respectable for my purposes, but how do I<br
/>correct this condition?? Can I ignore this / must live with it?<br />I have
tried three different MariaDB releases (10.0.19, 10.1.12, 10.1.24) to narrow
things down, but this message (x 1000&#39;s) is happening across all releases in
the Sysbench R/W phase.<br /><br />Here is the Sysbench command that drives the
workload against MariaDB -<br /><br />sysbench --test=lua/oltp.lua
--oltp_tables_count=128 --oltp-table-size=85937 --rand-seed=42 --rand-type=uniform
--num-threads=128 --oltp-read-only=off --report-interval=2
--mysql-socket=/var/lib/mysql/mysql.sock --max-time=201 --max-requests=0
--mysql-user=root --percentile=99 run<br /><br />Would anyone have a tip / idea
/pointer?<br /><br /><br />Regards,<br /><br /><br />JC<br /><br /><br />John
Cassidy<br /><br />Obere B&uuml;hlstrasse 21<br />8700 K&uuml;snacht (ZH)<br
/>Switzerland / Suisse / Schweiz<br /><br /><br />Mobile: +49 152 58961601
(Germany)<br />Mobile: +352 621 577 149 (Luxembourg)<br />Mobile: +41 78 769 17 97
(CH)<br />Landline: +41 44 509 1957<br /><br />http://www.jdcassidy.eu<br /><br
/>&quot;Aut viam inveniam aut faciam&quot; - Hannibal.