Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86842 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67413 invoked from network); 24 Jun 2015 10:29:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jun 2015 10:29:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.51 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.215.51 mail-la0-f51.google.com Received: from [209.85.215.51] ([209.85.215.51:36105] helo=mail-la0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 19/02-55790-4A68A855 for ; Wed, 24 Jun 2015 06:29:56 -0400 Received: by lacny3 with SMTP id ny3so23157440lac.3 for ; Wed, 24 Jun 2015 03:29:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LBSmM0qdeONgNHV3MNupPJVEZSlqDNdlD1gxJM4LdSw=; b=0M8H+t1RrgR+wcHTngGTgtv2I0pm3Ir+p66ck9STe6vddggcVb5Vc5hLiTD52aywP0 ZRBFwrFtoAsWZd5kDZxaCjZsf9hQD01JdvARpRAkA8/bGPxnpdhGmT9Sr74VMifBQ8ks fGMmhKsN/f3pf+rd34XO9EvqpVJMIEwQql7pvwOxbI9hKkZjIj0wIl5OapGp9Pv/YGUX 0czk8vEXg31aDV2yO4ifvgp0/NBj+TOONbBI6438vRtPPR3I6xT1xSJAollCwiRHT2Z9 T8z9JoeG7qELILosmGlRTwTh6Ch+BduLf0K1gcTIJHLOVxuVlSzywlC4+gJd76zQ/txu Q4gQ== MIME-Version: 1.0 X-Received: by 10.152.25.198 with SMTP id e6mr39107541lag.83.1435141793154; Wed, 24 Jun 2015 03:29:53 -0700 (PDT) Received: by 10.152.43.105 with HTTP; Wed, 24 Jun 2015 03:29:53 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Jun 2015 12:29:53 +0200 Message-ID: To: Yasuo Ohgaki Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=089e0160c150c88f50051940fc2a Subject: Re: [PHP-DEV] Move to Fast ZPP? From: tyra3l@gmail.com (Ferenc Kovacs) --089e0160c150c88f50051940fc2a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Jun 24, 2015 at 12:21 PM, Yasuo Ohgaki wrote: > Hi Ferenc, > > On Wed, Jun 24, 2015 at 6:21 PM, Ferenc Kovacs wrote: > >> it was meant as a performance optimization for the most heavy/hot >> codepaths. >> What gave you the idea that the situation changed and we should use it >> everywhere? >> > > I'm curious about the status of Fast ZPP and it's usage. > The RFC says it reduces function call overheads by 90% and > I didn't see reason why we shouldn't move to Fast ZPP. > > "For some really simple function like is_string() or ord() the overhead o= f > zend_parse_parameters() may be about 90%." > https://wiki.php.net/rfc/fast_zpp > > I'll use it for functions called many times. > > I wouldn't consider the likes of pg_fetch_* to be appropriate for for using Fast ZPP, even db heavy applications are unlikely to call it more than a houndred times per request, so the perf gain would be negligible compared to the increased cost of maintenance. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --089e0160c150c88f50051940fc2a--