Did I miss something, or is this not concerning a 1 second spike to 100%?
I do not see why this is problematic, and I'm a bit curious as to how it
is...
I mean, the DB does use 100% CPU if it's available. And for a 1 second
period,
it could very well just be the sample time for the tool monitoring it....
"Scott Pippin" <[EMAIL PROTECTED]>
05/05/2004 02:52 PM
To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
cc:
Subject: Re: MySQL 100% CPU Spikes
>Any information on how I can go about doing this, or maybe some
>documentation on improving the speed.
>The problem is two of the databases I think, both are around 1.1MB
each and:
Try putting an explain before your select statement:
http://dev.mysql.com/doc/mysql/en/EXPLAIN.html
this will show you if it is your query that is causing the problem.
>Database1: 13736 data records
>Database2: 77312 data records.
>Is this excessive ?
Not even close. We currently have a database of 4 gb and 75 tables.
One of our tables has over 2 million rows. Even this is small as
compared to some of the other databases I have seen. Hope this helps.
Scott Pippin
[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
