Re: [percona-group] CPU usage mysqld up to 80% with insignificant load after 1 week uptime

113 views
Skip to first unread message

Olivier Doucet

unread,
Oct 8, 2012, 8:14:55 AM10/8/12
to percona-d...@googlegroups.com
Hi Andrej,

You should graph several values to see if there is any changes in
MySQL behaviour :

run SHOW STATUS and graph following values :

connections
queries
Innodb_buffer_pool_pages_*
Threads_running

If I'd have to diagnose your situation without any more information, I
would first give a look at query cache, and try to disable it if it is
possible.

Olivier



2012/10/5 Andrej van der Zee <andrejv...@gmail.com>:
> Hi,
>
> We are experiencing some weird behavior on our Percona server. After Percona
> Server is running for a few days CPU% of the mysqld process increases up to
> 80%. After restarting Percona Server it drops immediately under 5%. There
> are no significant entries in slowqueries.log. Now we are worried what will
> happen when the load increases (expected very soon) and we would like to
> solve this asap.
>
> How can it be that CPU% drops so steep after restarting Percona Server? What
> would be the way to debug this issue?
>
> These are our specs:
> Server version: 5.5.27-28.0-log Percona Server (GPL), Release rel28.0,
> Revision 291
> Kernel: 2.6.32-220.13.1.el6.x86_64 BST 2012 x86_64 x86_64 x86_64 GNU/Linux
> Opsys: CentOS release 6.2 (Final)
>
> Than you,
> Andrej van der Zee
>
> --
> You received this message because you are subscribed to the Google Groups
> "Percona Discussion" group.
> To post to this group, send email to percona-d...@googlegroups.com.
>
>

Da

unread,
Oct 8, 2012, 8:15:12 AM10/8/12
to percona-d...@googlegroups.com
Don't really know if it could be that, but as once happened to me would be good to try...

It happened the same to me, the CPU goung crazy for no apparent reason. After lloknig everything I was quite dpressed as I could not find anything wrong in mysql... 

At the end I found the problem was at the "date/time". I was using an ntp server and something changed in it. Mysql didn't like the change as CPU was telling me...

What I did to solve it:
/etc/init.d/ntpd stop
date
date -s "jul 25 14:17:51 CEST 2012"
/etc/init.d/ntpd start

Don't know if it is your problem,.. but it was mine!
Reply all
Reply to author
Forward
0 new messages