ID: 34779 User updated by: jan dot lachman at stringdata dot cz Reported By: jan dot lachman at stringdata dot cz -Status: Feedback +Status: Open Bug Type: Output Control Operating System: WindowsXP PHP Version: 5CVS-2005-10-07 New Comment:
Ok. I use "standard" ab.exe(Win) or OpenSTA(Win) or Siege(from linux), etc on "client" side. On server side I have small script (like index.php) that includes: <? phpinfo(); sleep 5; ?> nothing else. How it works you know. I know that if my php use output_buffering = 4096 - our server goes down, but when I use output_buffering = On, it works perfectly! Previous Comments: ------------------------------------------------------------------------ [2005-10-24 00:28:55] [EMAIL PROTECTED] I have just tried 10000 connections to phpinfo() page an memory usage has stablized at around 21 MB for 10 concurrent connections. Please post a complite test script that would allow us to trace the problem. ------------------------------------------------------------------------ [2005-10-07 16:57:08] jan dot lachman at stringdata dot cz Nothing. I mean without change. With default value (output_buffering = 4096) bad, with output_buffering = On working perfectly. On request I may send screenshot of Task Manager (with-and-without directive). Thanks. ------------------------------------------------------------------------ [2005-10-07 15:39:08] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2005-10-07 14:53:26] jan dot lachman at stringdata dot cz Description: ------------ On MS Windows XP Pro (SP2) and Apache 2.0.5.4 has PHP(php5apache2.dll module) a serious problem with value output_buffering = 4096. When I start the web-server, then I run benchmarking programs (like siege or ab.exe or OpenSTA) and I try to access a small script that includes phpinfo (with 50-100 simulated user connections), I get memory load about 10MB within !one! minute (and growing) - until the RAM (715MB) is available. Then total crash follows after this. After two-days testing, we found (with my team-mate) little way to solve this problem. If we set output_buffering = On , it's working perfectly. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=34779&edit=1