#21903 [Fbk->NoF]: Parsing many include files on dual processor machines is very slow

ID: 21903 Updated by: sniper@php.net Reported By: tigger42@gmx.net -Status: Feedback +Status: No Feedback Bug Type: Performance problem Operating System: Windows 2000 AS / SP2 PHP Version: 4.3.0 New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2003-02-03 07:34:28] sniper@php.net What processors are those? ------------------------------------------------------------------------ [2003-01-29 10:19:49] tigger42@gmx.net same with CLI ------------------------------------------------------------------------ [2003-01-27 17:40:29] sniper@php.net Have you done any tests using the CLI binary? (to rule out the IIS factor) ------------------------------------------------------------------------ [2003-01-27 17:35:17] tigger42@gmx.net sorry for posting twice ------------------------------------------------------------------------ [2003-01-27 17:34:19] nospam@nospam.com processing include files with include_once ( these files containing classes only in our case ) takes huge amounts of time on dual processor machines. On a single processor machine (1ghz) the 30 include files are processed in about 0.2sec and on the dual processor machine (2*1ghz) it takes about 3.5sec. Using only include statements (not include_once) brought processing time down to 1.7sec which is still far from the 0.2sec on the UP machine. operating system: win2000as (sp2) webserver: iis php: 4.2.3 and 4.3.0 (maybe earlier also) standard win32-zip from php.net with extensions gd and oci8 enabled i've already looked through zend_execute.c but the only time consuming thing i saw was zend_fopen(). if you need further information contact me any time. ------------------------------------------------------------------------ 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/21903 -- Edit this bug report at http://bugs.php.net/?id=21903&edit=1