So your application tracks incoming HTTP-GETS. When you say that it's not able to "capture" all 1000 entries, what do you mean? Does an exception get thrown? Do some of the HTTP-GETs just not show in the database?
You need to provide alot more information: Do all the HTTP-GETs happen on the same connection? How long do the HTTP-GETs take to process? 10 seconds? What hardware are you running on? CPU, disk, memory. Is the machine dedicated to MySQL? What's the MySQL CPU load on the above hardware during your test What table type (InnoDB, MyISAM, BDB, etc)? What tuning have you done to the my.cnf, and are you sure that MySQL is using that my.cnf (ie is it in the correct location)? ----- Original Message ----- From: "mysql" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 15, 2004 9:23 AM Subject: MySQL Performance Tuning? > Hi Gurus, > I'm currently building an application which is expected > to take very high loads. What the app does is essence is > to 'log' and incoming entry into MySQL, do something then updates > the 'log' entry. > > To test MySQL in handling high load, I used siege > on another server to send 1000 HTTP GET requests to my php > script which then does as described above. The results that I'm > getting is not encouraging as it seems that MySQL is not able > to capture the 1000 entries. > > I've tried doing some of the tuning from the net but so > far to no avail. Does anyone know what is the critical tuning method > needed for MySQL to be able to handle loads like this? > > Thank you very much! > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
