Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96372
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain lerdorf.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAPZMMAsZHO+=XAFUWQsE5GNc8c16+fEZk_LTyn8y-X17QRFzhA@mail.gmail.com>
References: <CAPZMMAsZHO+=XAFUWQsE5GNc8c16+fEZk_LTyn8y-X17QRFzhA@mail.gmail.com>
Date: Sat, 15 Oct 2016 03:10:01 +0800
Message-ID: <CACXBjuiKuYp_OCWVPnoXdnY38vC5We7-QhiN8qv8Wd60TDVD4Q@mail.gmail.com>
To: jeremie.bordier@gmail.com
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113f9772812705053ed7fb96
Subject: Re: [PHP-DEV] Performance drops after some time, PHP7-FPM + Docker
From: rasmus@lerdorf.com (Rasmus Lerdorf)

--001a113f9772812705053ed7fb96
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 14, 2016 at 9:15 PM, J=C3=A9r=C3=A9mie BORDIER <jeremie.bordier=
@gmail.com>
wrote:
>
> I don't really know how to investigate further. If you have any
> pointers on how to help figuring out what's wrong, I'd love to try.
>

I would breakout the Linux perf command for something like this.

Run it like this:

perf record -p <pid_of_a_php-fpm_process> -g

Let that run for some arbitrary amount of time. Start with 10 seconds, or
so. Then:

perf report -n

That should give you a nice report of what your php-fpm process did for
those 10 seconds. Now do the same thing when you see the problem and
compare the reports.

-Rasmus

--001a113f9772812705053ed7fb96--