Well I probably can tweak the queries, but there are a LOT of them. It is for http://www.ecommstats.com so we get a TON of requests that have to processed with probably ~20 queries (selects, inserts, updates), then there is a maintenance program that runs every few minutes to clean things up and calculate some things which does several more queries and goes through to processe data. Most of the time it's ok, and it can handle it, but during some peak times, requests queue up and as long as there are requests in the queue, it's pinned. So I'm just trying to figure out how to best handle it.

> Any idea why?  Are you doing too many table scans?  Too much
> computation in the queries?  Lots of LIKE "%foo%" queries?

There is maybe 1 LIKE query and I'm sure that's not causing any issues.

Travis



Jeremy Zawodny wrote:

On Tue, Oct 21, 2003 at 08:59:31PM -0600, Travis Reeder wrote:

It seems mostly to be mysql pinned, not the app. like 99% mysql until all data is processed and keeps going up when data coming in is more than can be processed.


So MySQL is using 99% of the CPU?

Any idea why?  Are you doing too many table scans?  Too much
computation in the queries?  Lots of LIKE "%foo%" queries?

If the CPU is truly the bottleneck and you can't improve the
performance by tweaking queries and settings, then faster CPUs will
help.


What could I change in my.cnf to get better performance? I just have a default mysql install (4.0).


It's hard to say.

Jeremy


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to