|
From: Patrick D. <pat...@pa...> - 2006-04-22 17:16:19
|
Well I have done some more test (not purposfully). In the need to setup a development box for email/webserver, I copied my current php code over to the test machine, insteall php 5.1.2 (same as on other box), except as fast-cgi instead of in apache module. The http server is lighttpd vs apache. On the lighttpd machine I installed 0.9.5beta2, and haven't had any real issues with it. One time I did get the emalloc problem but I think that was more my fault than a fault of eaccelerator. Max proccess userspace is set around 1gig on this machine On the apache machine, it still refuses to load with 0.9.5beta2 installed on it. Max proccess userspace is set to 1.6gig on this machine I haven't seen php use more than 60megs in normal usage, except when I do stress tests on it that involve loading 300meg files into memory. On Sat, 15 Apr 2006, Patrick Domack wrote: > I did do a test without the optimizer, I can't remember the exact results, > except that it did still have problems. I think it still gave me the same > emalloc message. > > On Sat, 15 Apr 2006, Bart Vanbrabant wrote: > >> Patrick Domack wrote: >>> I have been setting up a new webmail site that uses php instead of perl. >>> >>> The php webmail is horde. I originally instealled php 5.1.2, with >>> eaccelerator 0.9.5beta1 >>> >>> After config, testing, patching, and stressing it, it all seemed to work >>> good, except two files eaccelerator complained about opline. Example: >>> >>> [22605] EACCELERATOR: PHP crashed on opline 420 of main() at >>> /usr/local/www/horde/kronolith/config/prefs.php:275 >>> >>> It seems after I reinstalled php 5.1.2 without a 16meg memory limit, it >>> stopped complaining (not sure if it is related or not). >>> >>> At this time I noticed 0.9.5beta2 was out, and instealled it. >>> With it I have been unable to load any horde php file at all. >>> >>> Error message from php: >>> FATAL: emalloc(): Unable to allocate 1969775421 bytes >>> >>> I tried to debug eaccelerator, but can only get as far as to see what >>> files it attempted to proccessed: >>> >>> EACCELERATOR hit: "/usr/local/www/horde/test.php" >>> EACCELERATOR hit: "/usr/local/www/horde/lib/core.php" >>> >>> >> >> Hello, >> >> Can you try to disable the optimizer? It seems like a bug that make the >> code or optimizer go in an infinite loop. >> >> gr, >> >> Bart >> >> -- >> Bart Vanbrabant <bar...@zo...> >> PGP fingerprint: 093C BB84 17F6 3AA6 6D5E FC4F 84E1 FED1 E426 64D1 >> >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > eAccelerator-developers mailing list > eAc...@li... > https://lists.sourceforge.net/lists/listinfo/eaccelerator-developers > |