Re: AW: limited threads to two but 25 waiting?!

2005-10-18 Thread Gleb Paharenko
Hello. Very often InnoDB provides a better performance in environment where a lot of concurrent SELECTs and UPDATEs. Check if the problem still exists if you change the engine of you tables from MyISAM to InnoDB. M.E. Koch wrote: > Hello: > > After haveing a look at the `show proce

AW: limited threads to two but 25 waiting?!

2005-10-17 Thread M.E. Koch
May my guess was not right. Thanx so far for the help!!! yours mathias >-Ursprüngliche Nachricht- >Von: Gleb Paharenko [mailto:[EMAIL PROTECTED] >Gesendet: Sonntag, 16. Oktober 2005 14:45 >An: mysql@lists.mysql.com >Betreff: Re: limited threads to two but 25 waiting?! &

Re: limited threads to two but 25 waiting?!

2005-10-16 Thread Gleb Paharenko
Hello. Please, send to the list your queries and CREATE statements for tables which are used by you queries. Include the output of SHOW PROCESSLIST. > 2. When writng in my.cnf the skip-bdb option still the server > reserves memmory for berklyDB aswell with innoDB. But writing > somthing wr

limited threads to two but 25 waiting?!

2005-10-16 Thread M.E. Koch
Hi, I have searched and tried and have no clue why the db on 4.1.11-Debian_4sarge2 behaves like this. I have no TABLE LOCK query anywhere in my code! About the server (LAMP/ 2x3Mhz, 4GB RAM) 1. prob. the mysql> show processlist gives me a list of 25 threads waiting for there work. even on heavy l