ID: 50571 Updated by: j...@php.net Reported By: millennium at qme dot nl -Status: Open +Status: Bogus Bug Type: MySQLi related Operating System: Windows Server 2003 PHP Version: 5.3.1 New Comment:
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.php.net/manual/ and the instructions on how to report a bug at http://bugs.php.net/how-to-report.php Previous Comments: ------------------------------------------------------------------------ [2009-12-25 00:41:08] paj...@php.net That's expected as mysqlnd uses php's stream. That brings a small overhead over raw sockets. ------------------------------------------------------------------------ [2009-12-25 00:39:23] millennium at qme dot nl If I move the connect and disconnect outside the loop, the speed is the (almost) the same. php 5.2.6: time: 0.27 secs, memory usage 0.15 MiB. php 5.3.1: time: 0.28 secs, memory usage 0.40 MiB. moving the connect inside the loop again (keeping the disconnect outside) php5.2.6: time: 1.82 secs, memory usage 0.15 MiB. php5.3.1: time: 31.11 secs, memory usage 0.40 MiB. So I guess it's the connect. ------------------------------------------------------------------------ [2009-12-25 00:25:35] scott...@php.net Can you adjust your test to see if its the connection, the query or the closing that's causing the problems? ------------------------------------------------------------------------ [2009-12-24 23:26:32] millennium at qme dot nl C:\php2>php sync.php time: 28.37 secs, memory usage 0.40 MiB. C:\php2>php -v PHP 5.3.2-dev (cli) (built: Dec 22 2009 09:57:39) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2009 Zend Technologies ------------------------------------------------------------------------ [2009-12-24 23:19:05] j...@php.net Please try using this snapshot: http://snaps.php.net/php5.3-latest.tar.gz For Windows: http://windows.php.net/snapshots/ ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/50571 -- Edit this bug report at http://bugs.php.net/?id=50571&edit=1
