Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89477 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87493 invoked from network); 28 Nov 2015 08:38:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Nov 2015 08:38:03 -0000 Authentication-Results: pb1.pair.com header.from=martin.keckeis1@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=martin.keckeis1@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.54 as permitted sender) X-PHP-List-Original-Sender: martin.keckeis1@gmail.com X-Host-Fingerprint: 209.85.215.54 mail-lf0-f54.google.com Received: from [209.85.215.54] ([209.85.215.54:35198] helo=mail-lf0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 97/8D-04444-AE769565 for ; Sat, 28 Nov 2015 03:38:03 -0500 Received: by lfdl133 with SMTP id l133so148353337lfd.2 for ; Sat, 28 Nov 2015 00:37:58 -0800 (PST) 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=gj2ZFCye7PiLyDSzs6HW4WozHZvqLM+V6ARBWjjdCps=; b=tQzdRvr4pdjhvQELpCuvYQ/0wEdwjQCSaXhnRIKSoatN9t54qmXU9k0hKsmln3bwyl 5mUMKGZyAFHCRrhkpCvaLvro6wPsjYR0DURtvrEheZsjB2dZITUPvChzbXnYIEjMEBPo NiK5l2EcIFwnm8bk0HysikcPKdwv5pmLbzXHy98sQ47kURx7JqF7nKPJXVmKXfjqp680 TQEt3S0zHTZOwA1JVQ9u3rYEQOBNNBMO1vulWzn+u/ydPwelaqYrFHBTaDg2+5cQr3n/ X1mZ/U/TErqJx2KEH+7A5kCiNWBWYhfbfZT+aB12T3V5g5GJ8Oo4Xjqxph2eSo3U4ekk Hh6Q== MIME-Version: 1.0 X-Received: by 10.112.158.66 with SMTP id ws2mr22292769lbb.126.1448699878816; Sat, 28 Nov 2015 00:37:58 -0800 (PST) Received: by 10.25.21.27 with HTTP; Sat, 28 Nov 2015 00:37:58 -0800 (PST) Received: by 10.25.21.27 with HTTP; Sat, 28 Nov 2015 00:37:58 -0800 (PST) In-Reply-To: References: <009301d128fa$bb2675d0$31736170$@lool.fr> <1448631693.24066.10.camel@kuechenschabe> Date: Sat, 28 Nov 2015 09:37:58 +0100 Message-ID: To: Jan Ehrhardt Cc: PHP internals Content-Type: multipart/alternative; boundary=001a11c34006a9c0ab052595b9e0 Subject: Re: [PHP-DEV] Proof of Concept : 3.5x and more Performance Boost for php7 using 4 cores From: martin.keckeis1@gmail.com (Martin Keckeis) --001a11c34006a9c0ab052595b9e0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 27.11.2015 9:35 nachm. schrieb "Jan Ehrhardt" : > > Johannes Schl=C3=BCter in php.internals (Fri, 27 Nov 2015 14:41:33 +0100)= : > >On Fri, 2015-11-27 at 11:02 +0100, Pascal KISSIAN wrote: > >> > >> I made a simple test to know if it was possible to speed-up php > >> performance by using parallel programming. > > > >Your test runs a single PHP process. Mind that in a typical deployment > >on a server you have quite a few parallel PHP processes already > >competing for time on the CPU (when not waiting for IO) a benchmark > >should reflect that. > > In most cases that is true. But not always: we have an application that > uses PHP for matching a lot of profiles with a couple of hundred job > opportunities. Despite a lot of optimizations it drills down to a single > PHP thread doing the bulk of the processing. We even chose a processor > with a high single thread score when we had to buy a dedicated server to > run this application, using these charts: > http://www.cpubenchmark.net/singleThread.html > > So anything that makes PHP using more cores would be very welcome. > Preferably it has to be transparent, i.e. without extra coding like > starting up more threads using the php threads extension. > -- > Jan > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > Maybe a bit offtopic, but for that jobqueue and workers were designed? So you could use multiple workers? Or is it not possible there? --001a11c34006a9c0ab052595b9e0--