<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">2013/1/8 Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
You probably are using ext3 with barriers. Please check:<br>
<br>
cat /proc/mounts<br>
<br>
and if you don't see "barrier=0", you're using barriers.<br></blockquote><div><br></div><div>I was in fact using barriers. I edited my fstab:<br>UUID=f1f1cbe3-ef25-4dd5-b3ed-35deca2eeb37 / ext3 barrier=0,noatime,errors=remount-ro 0 1<br>
<br>I remounted and /proc/mounts says:<br> /dev/disk/by-uuid/f1f1cbe3-ef25-4dd5-b3ed-35deca2eeb37 / ext3 rw,noatime,errors=remount-ro,data=ordered 0 0<br><br></div><div>(I don't think /proc/mounts is supposed to say barrier=0, but rather data=ordered?)<br>
<br></div><div>However it only helped av very small amount. mysqld still uses 100% CPU while "Reschedule requested for MATCH 0 0 0 - EITScanner", but now "only" for 80 seconds compared to the earlier 90-100 seconds. <br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I'm also guessing you're using the unsupported InnoDB storage engine. InnoDB usage requires very specific configuration to get acceptable performance.<br>
</blockquote><div><br></div><div>All my tables (except weather*) uses MyISAM so this does not seem to be where the problem is hiding.<br><br></div><div>Other suggestions?<br></div></div><br clear="all"><br>-- <br>Jarle Thorsen
</div></div>