On Thu, Jun 06, 2002 at 02:24:06PM -0700, Matt Rowe wrote: > Dear list, > > After doing a good bit of reading, the details are still hazy. > > I have a web-based application (about 20 tables, with up to 100,000 > records per table - but most tables are much smaller). 99% of > "select" queries are very very fast.
Great. > However, there is the occasional "select" query that requires a good > amount of work on the database. Why? Can it be optimized? > It may take a few seconds to return. This is okay, however, these > queries drastically affect the performance of other users. Right. > Is there a smart way to "limit system resources per thread"? Nope. > I'd much rather have the long-query person wait an extra few seconds > than have several short-query people wait. I've tried tuning all > the typical parameters, but I don't think the logjam is memory-based > (the hard disk doesn't move). Hmm... Have you tried making the slow query a LOW_PRIORITY one? Jeremy -- Jeremy D. Zawodny, <[EMAIL PROTECTED]> Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.51: up 8 days, processed 192,918,088 queries (270/sec. avg) --------------------------------------------------------------------- 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
