Hello everyone.

My problem: i wrote a multithreaded app (C++) which uses mysql database (Server version : 4.1.13-standard-log, linux RedHat 8 2.4.29 #1 SMP Thu Mar 10 03:05:14 EET 2005 i686 i686 i386 GNU/Linux). Most of the treads are staying for extended amounts of time in rt_sig state. After processing several hundreds of records, queries are becoming exteremely slow. Any help, suggestion is welcome !

I have writen a multi-process app instead of a multi-threaded server app that connects to mysql server. Although it may not be exactly the same, my queries are becoming slow after some time and even having some timeouts. It turns out that I have set "max_connections" to a high number. I followed some recommnedations from mysql site regarding settings of max_conections and set it at a lower number.

The result, queries are handled well (not slow) and no timeouts. It may not be your C++ app but could be the mysql settings thats causing the problem

Hope this helps.

ferdinand

Are you closing your connections (or returning them to a connection pool)? Unless your queries are very long running or you have a high-throughput system you should be fine with a dozen or so connections for most uses. If your high-water-mark of open connections is higher than that, be suspicious that you are not closing them. Another hint would be if the mysql memory footprint grows and grows.

thx guys, to all of U ;-)