Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98959 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35457 invoked from network); 3 May 2017 11:32:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 May 2017 11:32:51 -0000 Authentication-Results: pb1.pair.com smtp.mail=lists@rhsoft.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=lists@rhsoft.net; sender-id=pass Received-SPF: pass (pb1.pair.com: domain rhsoft.net designates 91.118.73.15 as permitted sender) X-PHP-List-Original-Sender: lists@rhsoft.net X-Host-Fingerprint: 91.118.73.15 mail.thelounge.net Received: from [91.118.73.15] ([91.118.73.15:28347] helo=mail.thelounge.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3D/41-02776-2EFB9095 for ; Wed, 03 May 2017 07:32:50 -0400 Received: from rh.thelounge.net (Authenticated sender: h.reindl@thelounge.net) by mail.thelounge.net (THELOUNGE MTA) with ESMTPSA id 3wHwxp1NYkzXMn for ; Wed, 3 May 2017 13:32:46 +0200 (CEST) To: Mailing-List php References: <79ca3537-b439-583a-6162-05da302711f2@rhsoft.net> <403881ad-ec0c-395f-279e-6b345ee7cb39@rhsoft.net> <84d53625-de7f-e2cb-e2c7-c3e83ede6219@rhsoft.net> Message-ID: Date: Wed, 3 May 2017 13:32:45 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-CH Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] the experimental jit-branch is impressive From: lists@rhsoft.net ("lists@rhsoft.net") Am 03.05.2017 um 13:20 schrieb Eli: >>> Would you mind running some numbers against "commodity >>> apps/frameworks" (e.g. Wordpress, ZendFramework, Laravel, etc...) I >>> expect that will be far more telling (in a potentially positive way). >>> For example, HHVM performs best on "highly optimized code", which is >>> why it tends to look a bit tepid against PHP 7 when run on "normal" >> >> sorry, all my setups have a lot of stuff in the config to kill stuff like wordpress/joomla/typo3 so nobody comes to the idea installing after that badly mainatined stuff on my machines (for our own CMS there is a deplyoment system maintaining 100, 200 or 1000 instances with s single shell command) > > However the majority of PHP in the wild is in fact running on these commodity frameworks. Especially Wordpress. > > So if your numbers don't show the benefit there. Or even show a decrease. Then it's going to be rough moving forward. well, i think it's also valueable to know that the JIT don't harm or even improve slightly code which is not mainstream and has already a small footprint for wordpress, joomla and other mainstream software people which use it in their daily workflow are the better ones for setup demosystems compared to when i loveless setup soemthing probably never used that way in real life what i can offer is everytime when the GIT branch get noticeable changes to fireup a build and watch how it envolves here in case of performance