Re: [PHP4BETA] Trouble with Oprimizer

if i recall correctly, Zend is supposed to be releasing some kind of intermediary compiler later this year. -- Brendan W. McAdams | Home/Cell: (305)401-7313 Programmer/Systems Administrator | Work: (305)377-2880 Plexus InterActive | email:brendan@plexmedia.com http://www.plexmedia.com "Always listen to experts. They'll tell you what can't be done, and why. Then do it. " -- Robert A. Heinlein ----- Original Message ----- From: "Andreas Pour" <pour@mieterra.com> To: "PHP4 Beta List" <php4beta@lists.php.net> Cc: <chabotc@nait.nl> Sent: Saturday, April 01, 2000 1:27 AM Subject: Re: [PHP4BETA] Trouble with Oprimizer Chris Chabot wrote: > > My main question would be, how large is this script? ive found that in many > cases, loading & preparsing a large code base is the main bottleneck, and > not the script execution time. > As im sure uve read in the description of the optimizer, its a _multi > parse_ optimizer, so the script load time only increases. Ive got the same > problem here with a 140Kb script :) What would be awesome is a facility to convert php scripts to bytecode. It's an avoidable waste of resources to be parsing the same large scripts every time someone hits a page. Anyone have an idea know how hard it would be to add a bytecode generator/parser into the php frontend (it could even automatically check timestamps to make sure the bytecode is newer than the script)? Probably the better place to put the bytecode generator is in Zend engine (post-optimization), but the license seems to be unfavorable. Ciao, Andreas -- PHP 4.0 Beta Mailing List <http://www.php.net/version4/> To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net For additional commands, e-mail: php4beta-help@lists.php.net To contact the list administrators, e-mail: php4beta-admin@lists.php.net