Every now and then, mysqld (5.0.22) jumps to 95%+ cpu usage and stays there. Seems to be a common issue, as far as google can tell, but details are alarmingly vague, and some people seem to suggest that it''s a bad query causing it. How do I go about determining if it''s something my application is doing? martin
development.log has all the SQL statement available for view.. I''d bring this one to the mysql list tho. -- Posted via http://www.ruby-forum.com/.
Also if the cpu usage is high for a sustained period, try running ''mysqladmin processlist'' from the command line and you''ll see exactly what''s happening while it''s running at high load. Ross On 7/20/06, Brez! !! <jbresnik@gmail.com> wrote:> development.log has all the SQL statement available for view.. I''d > bring this one to the mysql list tho. > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Ross Riley riley.ross@gmail.com