ID: 13094 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: Performance problem Operating System: Windows 2000 PHP Version: 4.0.6 Assigned To: sniper New Comment:
Has this problem been solved in the update for 4.1.2? Previous Comments: ------------------------------------------------------------------------ [2001-10-28 12:34:17] [EMAIL PROTECTED] This should be fixed in CVS now. You can try the latest development build from http://www.php4win.com/ but make sure it's dated after 27th of October 2001. Also, there are some minor leaks still in the new code. If you encounter such leaks, please send the shortest possible code + html with which you can reproduce the leak to [EMAIL PROTECTED] (or me) so we can get rid of these leaks. The fix will be in PHP 4.2.0. --Jani ------------------------------------------------------------------------ [2001-10-28 12:10:12] [EMAIL PROTECTED] Fixed in CVS by Jani, will be fixed in 4.2.0 ------------------------------------------------------------------------ [2001-09-02 16:52:23] [EMAIL PROTECTED] Work in progress... ------------------------------------------------------------------------ [2001-09-02 11:57:36] [EMAIL PROTECTED] This has nothing to do with 2291. The problem probably is that PHP takes all HTTP-post data into it's memory, and only after the complete header (WITH all files) are in-memory, php_mime_split is called to get the files out of the request and save them to disk. So if you need to recieve file-uploads of 100MB or something, PHP needs 100MB of RAM... otherwise it will swap and thus be terribly slow (especially on Windows) A real solution would be to rewrite php_mime_split to run on-the-fly... which at first glance isn't terribly hard. ------------------------------------------------------------------------ [2001-09-02 11:17:11] [EMAIL PROTECTED] Seems duplicate of 2291, but that one should be fixed in 4.0.6 ------------------------------------------------------------------------ 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/13094 -- Edit this bug report at http://bugs.php.net/?id=13094&edit=1
