We have the following problem: on the server (quite fast) we have the Mysqld-nt daemon running ; and the data resides in it. When a user access the server with a very long query and another try to do the same , but with a very simple query ; the last one has to wait a very long time because of the first query takes almost all the resources (100% CPU time ....when it should not !) ...when normally it would take 2 or 3 seconds... Is there a way ( some variables to set , some specific commands,OS configuration or whatever!) to make the server stop for a while the thread concerned with the long query , execute the simple query , and return back to its job?...in short: how could we optimize and better balance the server load ?
We tried several solution , like changing variables like key_buffer_size , join_buffer_size etc. Change some TEXT fields in CHAR fields but it does not seem to work . You know where the problem is ?...if in a big office one launch a long query ( in our case it could happen) the other clients are almost stuck! TIA C. P.S. We use a Visual Basic-like programming language to build our application , and we access the data via MyODBC 2.5 and ADO. Normally the LAN we are dealing with are of peer-to-peer type. __________________________________________________________________ Tiscali ADSL. Scopri la fantastica promozione di Natale: tutto Gratis fino al 9 gennaio! Abbonati ora: prima ti abboni, pił risparmi! http://point.tiscali.it/adsl/index.shtml --------------------------------------------------------------------- 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
