Hi Marc, Thanks for the suggestion. I hope you would be kind enought to provide another. My application is "transactional", in the business sense, in that, at the point of sale, the transactions must be quick. So inventory must be updated quickly to move the people through the line. The question is would not UPDATE LOW PRIORTY make the UPDATES then wait for any slow selects to finish before proceeding, thus making the point of sale pontentialy suffer? Maybe I don't understand UPDATE LOW PRIORITY.
I think in my case I have conflicting requirement, but the main focus is to move the people at the cash register out the door :) These are ususaly very quick and short queries. This conflicts with reporting and product ordering and even data mining. Which in my case could be given a low priority, but not if it locks tables, or even run without locking (as our old system did!). Any advice or discussion is appreciated. Thanks, Ken ----- Original Message ----- From: "Marc Prewitt" <[EMAIL PROTECTED]> To: "Ken Menzel" <[EMAIL PROTECTED]> Cc: "°í¼ø¹Î" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, April 07, 2002 6:43 PM Subject: Re: How can I kill the slow query automatically? > Without setting up replication, you could use 'UPDATE LOW PRIORITY': > > http://www.mysql.com/doc/U/P/UPDATE.html > > If you do setup replication, you can set the replica database to use low > priority updates too by using the --low-priority-updates option to mysqld: > > http://www.mysql.com/doc/C/o/Command-line_options.html > > You should try both of these before switching to innodb as the performance > is not as fast as myisam. > > -Marc > > Ken Menzel wrote: > > > > Hi, > > There is no way to kill slow queries autmatically unless you were to > > write a script (maybe in perl or php?) to do this job. I have a > > similar problem and am thinking of replicating the database just to > > avoid this problem. I would then direct certain type of queries to > > the replicated server. The issue I have is I need selects not to lock > > the table for update! On FreeBSD this seems also to cause the CPU > > usage to jump very high. > > > > I was thinking of writing some test scripts, but I think the real > > answer for both of us may be to change to the InnoDB table type. Have > > you tried this? use ALTER TABLE type=innodb, after you have intalled > > mysql-max and created the tablespace. > > > > I hope this helps, > > Ken > > > > ----- Original Message ----- > > From: "°í¼ø¹Î" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, April 03, 2002 5:28 AM > > Subject: How can I kill the slow query automatically? > > > > > My DB has many update queries and a few select queries. > > > Sometimes select queries take very long time so update can't > > > proceed. I can kill the select query manually. But I can't check > > > the status all the time. > > > > > > Are there any ways to kill slow query automatically? If you know, > > > please let me know. Any information will be appreciated. > > > > > > > > -------------------------------------------------------------------- - > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
