(description of the situation first, question at the end) Using: - MySQL-3.23.49a - Linux Red Hat 7.2 (SGI XFS patch) - 2xPIII/700, 1GB RAM, 4x36GB SCSI RAID5, Mylex DAC960
The system runs a custom syslogd ( http://sourceforge.net/projects/msyslog/ ) that logs the messages in MySQL instead of text files. At this moment, 30 systems send logs over the network to this server. Because the way i configured msyslog, i have one connection from msyslogd to MySQL for each host, logging to its own separate database (long story, don't ask). So, basically, i have 30 client connections doing a lot of INSERT DELAYED's, each one in its own database. The machine has load issues. The idle CPU is around 25%, but load average is around 1.00 but sometimes it goes beyond 2.00, and "system" CPU usage (kernel) is around 20..50%. The "user" CPU usage is very low (<10%). I cannot let it go beyond 2.00 load average, because then i risk losing syslog messages. I'm trying to reduce the load average. It's not the disk I/O or network I/O, i checked that with vmstat. But the system is doing a lot of context switches: 1000 / sec, sometimes more. So, i think the machine spends too much time just with switching context between threads. My question is: what's the reasonable limit of the number of client connections to a MySQL server? Am i going to get any benefit from upgrading to MySQL-4.0? -- Florin Andrei "The world is full of bad security systems designed by people who read 'Applied Cryptography'." - Bruce Schneier --------------------------------------------------------------------- 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
