Re: Re[5]: [PHP-DEV] Design of the Zend Engine's Instruction Set

From: Date: Fri, 21 Aug 2009 17:03:38 +0000
Subject: Re: Re[5]: [PHP-DEV] Design of the Zend Engine's Instruction Set
References: 1 2 3 4 5 6 7  Groups: php.internals 
Request: Send a blank email to internals+get-45327@lists.php.net to get a copy of this message
I have measured Quercus php performance compared to standard php with APC on a ecommerce workload and found that Quercus php performed slower than standard php + APC. Regards, Basant. On Aug 16, 2009, at 11:16 AM, Tom Boutell wrote:
Re: the performance of PHP, if it's badly implemented, shouldn't Quercus (a reimplementation of PHP in Java) run rings around it? In reality, Quercus is faster than PHP without APC, but with APC the Quercus team themselves admit it only "roughly matches" the original PHP in speed. http://www.caucho.com/resin-3.0/quercus/ I guess you could spin this the other way though. Java optimizes well, but not as well as raw C. Standard PHP, being implemented in raw C, ought to have some performance advantages over a reimplementation in Java. But apparently not so much. On Sun, Aug 16, 2009 at 1:53 PM, Lothar Scholz<scholz@scriptolutions.comwrote:
Hello Paul, PB> Yes, by many times. Part of that might be the expense of PHP's weak PB> typing and references. No. Smalltalk, Javascript, Lua they all have the same problem with it and they solve it in much more clever and performant ways. Javascript with its class free OO is even harder and with V8 they have a much much better solution. It's just the implementation - not the language. PB> They cause most operations to be more PB> expensive, even if they are not used in that particular operation. PB> I did a performance analysis of PHP in a paper I have in submission. PB> You might find it interesting (comment welcome): PB> https://www.cs.tcd.ie/~pbiggar/wip-sac-journal.pdf. Thanks, just had a 10min quick look at it - hope to find some more time later. And first of all begin a tool writer (IDE Developer) myself i can't agree more about the problems with "the source is the specification" idea. <Strong Language Warning> This sucks so huge and is such a fucking lazy argument of an incompetent language development team. By the way greetings to Matz and his team who also sucks with his CRuby. I really questioning the skills of a lot of core programmers when i read the PHP manual section about namespaces. Simple questions about scopes of identifier aliasing - nothing of this is specified. A buggy implementation should solve as reference? Damn'd fucking college boys. This was an acceptable development method for PHP3. </Strong Language Warning> Okay i must cool myself down. I've seen that you talked about branch prediction misses in your paper. Did you ever tried to compile the original PHP with different compilers, for example from intel or sun studio? Did you test or have you ever heard of someone who tested the influence of the profiling feedback that modern C compilers offer? (Well don't ask me - it's somewhere on my TODO list - but i also haven't had the time yet). -- Best regards,
 Lothar Scholz                mailto:scholz@scriptolutions.com
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
--Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php


« previous php.internals (#45327) next »