#19030 [NEW]: performance issues with mysql extension

From: Date: Thu, 22 Aug 2002 04:11:13 +0000
Subject: #19030 [NEW]: performance issues with mysql extension
Groups: php.bugs 
Request: Send a blank email to php-bugs+get-17493@lists.php.net to get a copy of this message
From: bob@bravenet.com Operating system: Any PHP version: 4.2.2 PHP Bug Type: Feature/Change Request Bug description: performance issues with mysql extension When establishing a persistent connection, if PHP finds an existing connection it will do a mysql_stat() on the link that it found and then check the error for CR_SERVER_GONE_ERROR then reconnects on failure. I believe mysql's C API has a better function to do what is performed. The mysql_ping() api function will perform the same functionality at a lower cost in performance. The original host/port/user/pass information should be retained in the mysql link structure so that a failed mysql_ping() will reconnect automatically to the database server. This also removes the logging entry caused by a mysql status command. This does have an impact for sites with a higher load. Thanks for you consideration on this. -- Edit bug report at http://bugs.php.net/?id=19030&edit=1 -- Try a CVS snapshot: http://bugs.php.net/fix.php?id=19030&r=trysnapshot Fixed in CVS: http://bugs.php.net/fix.php?id=19030&r=fixedcvs Fixed in release: http://bugs.php.net/fix.php?id=19030&r=alreadyfixed Need backtrace: http://bugs.php.net/fix.php?id=19030&r=needtrace Try newer version: http://bugs.php.net/fix.php?id=19030&r=oldversion Not developer issue: http://bugs.php.net/fix.php?id=19030&r=support Expected behavior: http://bugs.php.net/fix.php?id=19030&r=notwrong Not enough info: http://bugs.php.net/fix.php?id=19030&r=notenoughinfo Submitted twice: http://bugs.php.net/fix.php?id=19030&r=submittedtwice register_globals: http://bugs.php.net/fix.php?id=19030&r=globals

« previous php.bugs (#17493) next »