Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96491 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74022 invoked from network); 19 Oct 2016 14:38:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Oct 2016 14:38:26 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain lerdorf.com designates 209.85.223.181 as permitted sender) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.223.181 mail-io0-f181.google.com Received: from [209.85.223.181] ([209.85.223.181:33241] helo=mail-io0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AC/DA-14749-F5587085 for ; Wed, 19 Oct 2016 10:38:25 -0400 Received: by mail-io0-f181.google.com with SMTP id q192so33798137iod.0 for ; Wed, 19 Oct 2016 07:38:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lerdorf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zgZXg1kfb5vPX1rqpetRwhHTtgzEPAwApcbSfrwcrEM=; b=jTfv3MmDH3ZnA2jTflhzie/VsaO2ARbYcyhaWAnnUN/ScRvQAiH/Bt/C9ClQVjdGar A7jx6DREMdlpcyWvwxmG8ypkH/cZz6va2aKbP+887K147OaibF1af19vJtphFVsvk8NL bDoD2+pg/hrL3rRF0opo5APWD2qW/eKwHSaWBcZsADIranH7dRiTGvWlh8emOmkTIb7A i2F/S2UdANQanpTHSLCgP/dF2xzblRgg6T9Kc8sLtQd2PQSt8MTAs6Z4jMvwzeOUtVJd y3HTalCussn1NNvwFt4raqnLVtPiRHHC5TPMzYf831EJ+hEWnQ4AetaGVRomYluSDI1F lQ2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zgZXg1kfb5vPX1rqpetRwhHTtgzEPAwApcbSfrwcrEM=; b=Eo2JbhvO/iecLK9buYtkmHkT9ja1mYh9G6P3DtkYCU6JjsPFNBjcJvLaXqUasL/40M UnzOOxVmQkeuC5x9X8Y0A5BlMFSe8IjJhhxW3EtWEUaxrNrqtKTIMAE8eeWhlprLg9Me gYDk1bgZuv3RbJ1rvTiMuRnvtkWRbetu83xC19xr0k65s30+h9H3KBB+FyxVK0mWo+fe PntjcBt8HO0geJBe68k1uHE1/x3axkKeTBV2AJeYD2nu7BpgDFamawQ8s/vXBzLOpHJM Kd/JDmLaWMl67BERpkkcgBMBR6WmRjXq8dxLeFXAcFTVBuf6Hasgy1nUk93FdyMIdJaY jNdQ== X-Gm-Message-State: AA6/9RmVdTnh4ACvl40XhIb5eNW8yFi+4JsPobkj8Ri67jCoexPs3ntZssjmQm4mWqJsg4GXRh60EvYsZFZ1mQ== X-Received: by 10.107.128.205 with SMTP id k74mr7270579ioi.223.1476887901316; Wed, 19 Oct 2016 07:38:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.138.195 with HTTP; Wed, 19 Oct 2016 07:37:40 -0700 (PDT) In-Reply-To: References: Date: Wed, 19 Oct 2016 07:37:40 -0700 Message-ID: To: =?UTF-8?B?SsOpcsOpbWllIEJvcmRpZXI=?= Cc: PHP internals Content-Type: multipart/alternative; boundary=001a113f9772bc6186053f38c22b Subject: Re: [PHP-DEV] Performance drops after some time, PHP7-FPM + Docker From: rasmus@lerdorf.com (Rasmus Lerdorf) --001a113f9772bc6186053f38c22b Content-Type: text/plain; charset=UTF-8 > > The output of the perf diff is quite poor I think, here's the mainline : > 35.90% +44.94% php-fpm [.] 0x0000000000042412 > 10.72% -6.05% libc-2.19.so [.] 0x0000000000079030 > 9.71% -9.34% newrelic.so [.] 0x0000000000030980 > 3.81% -3.47% [kernel.kallsyms] [k] ipt_do_table > 2.56% -2.02% [kernel.kallsyms] [k] nf_iterate > 2.32% -1.99% opcache.so [.] 0x0000000000008cec > 1.44% [kernel.kallsyms] [k] update_cfs_shares > 1.42% [kernel.kallsyms] [k] __bpf_prog_run > 1.28% [vdso] [.] __vdso_gettimeofday > > How could I provide more info ? > Yes, not much to go on there. But newrelic.so stands out to me. Can you try removing newrelic and see if it still happens? If it does, your next step is to look at the timing of a request. I usually do that with something like this: sudo strace -Ff -ttt -T -p 2>&1 | tee strace_output_file Do that on a fast process and on a slow process and let it run for a little while to the point where you think you have captured similar requests in both runs, then have a look at the timing between syscalls in both and see if you can spot if it is an isolated delay in a certain part of the request or if it is just an overall slowdown. I would also run: vmstat 1 both before and after. This gives you a picture of the overall health of your server. The si/so columns, for example, will tell you if you are swapping. If something has eaten a ton of memory and your system has started swapping more than before then that could also explain this. -Rasmus --001a113f9772bc6186053f38c22b--