#21903 [Fbk-Opn]: Parsing many include files on dual processor machines is very slow
ID: 21903 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: Open Bug Type: Performance problem Operating System: Windows 2000 AS / SP2 PHP Version: 4.3.0 New Comment: same with CLI Previous Comments: [2003-01-27 17:40:29] [EMAIL PROTECTED] Have you done any tests using the CLI binary? (to rule out the IIS factor) [2003-01-27 17:35:17] [EMAIL PROTECTED] sorry for posting twice [2003-01-27 17:34:19] [EMAIL PROTECTED] 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. [2003-01-27 10:42:18] [EMAIL PROTECTED] 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. -- Edit this bug report at http://bugs.php.net/?id=21903edit=1
#21903 [Opn]: Parsing many include files on dual processor machines is very slow
ID: 21903 User updated by: [EMAIL PROTECTED] -Reported By: [EMAIL PROTECTED] +Reported By: [EMAIL PROTECTED] Status: Open Bug Type: Performance problem Operating System: Windows 2000 AS / SP2 PHP Version: 4.3.0 New Comment: sorry for posting twice Previous Comments: [2003-01-27 17:34:19] [EMAIL PROTECTED] 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. [2003-01-27 10:42:18] [EMAIL PROTECTED] 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. -- Edit this bug report at http://bugs.php.net/?id=21903edit=1
