Welcome! Log In Create A New Profile

Advanced

Understanding the slow log stack trace

Posted by Mark van der Velden 
Mark van der Velden
Understanding the slow log stack trace
December 12, 2013 05:14AM
Hi,

I'm trying to make sense of the stack trace of PHP-FPM's slow log feature.
But I'm not sure how I should interpret it.

I notice that some of the stack traces in my log start (or actually end,
since the ordering is most recent on top) with a __construct() call, this
confuses me. What does the top item in the list represent?

A) Is it: That specific call took longer than the configured time limit,
the stack simply shows all calls before it
B) Or is it: The entire stack exceeded the time limit, due to the sum of
that call including all previous. The top most call is simply the one going
over the threshold. There might be calls after it, but those are not shown
C) Or is it: This is the entire stack of the request, that in total took
longer than the configured time, no calls came after it.

Stack trace gist: https://gist.github.com/Dynom/156e5fa1217ce527dd39


Thanks for reading.

--

---
You received this message because you are subscribed to the Google Groups "highload-php-en" group.
To unsubscribe from this group and stop receiving emails from it, send an email to highload-php-en+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Understanding the slow log stack trace
December 12, 2013 05:28AM
It means the entire stack exceeded the time limit.

The time when the backtrace was taken, minus the time when php started to
handle the request, is equal to the defined time limit.
2013年12月12日 下午1:12于 "Mark van der Velden" <markvdv@gmail.com>写道:

> Hi,
>
> I'm trying to make sense of the stack trace of PHP-FPM's slow log feature..
> But I'm not sure how I should interpret it.
>
> I notice that some of the stack traces in my log start (or actually end,
> since the ordering is most recent on top) with a __construct() call, this
> confuses me. What does the top item in the list represent?
>
> A) Is it: That specific call took longer than the configured time limit,
> the stack simply shows all calls before it
> B) Or is it: The entire stack exceeded the time limit, due to the sum of
> that call including all previous. The top most call is simply the one going
> over the threshold. There might be calls after it, but those are not shown
> C) Or is it: This is the entire stack of the request, that in total took
> longer than the configured time, no calls came after it.
>
> Stack trace gist: https://gist.github.com/Dynom/156e5fa1217ce527dd39
>
>
> Thanks for reading.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "highload-php-en" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to highload-php-en+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

--

---
You received this message because you are subscribed to the Google Groups "highload-php-en" group.
To unsubscribe from this group and stop receiving emails from it, send an email to highload-php-en+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Mark van der Velden
Re: Understanding the slow log stack trace
December 12, 2013 06:48AM
Hi Mauro,


On 12 December 2013 11:26, Mauro Stettler <mauro.stettler@gmail.com> wrote:

> It means the entire stack exceeded the time limit.
>
> The time when the backtrace was taken, minus the time when php started to
> handle the request, is equal to the defined time limit.
>
Excellent, thanks for clearing that up !



> 2013年12月12日 下午1:12于 "Mark van der Velden" <markvdv@gmail.com>写道:
>
> Hi,
>>
>> I'm trying to make sense of the stack trace of PHP-FPM's slow log
>> feature. But I'm not sure how I should interpret it.
>>
>> I notice that some of the stack traces in my log start (or actually end,
>> since the ordering is most recent on top) with a __construct() call, this
>> confuses me. What does the top item in the list represent?
>>
>> A) Is it: That specific call took longer than the configured time limit,
>> the stack simply shows all calls before it
>> B) Or is it: The entire stack exceeded the time limit, due to the sum of
>> that call including all previous. The top most call is simply the one going
>> over the threshold. There might be calls after it, but those are not shown
>> C) Or is it: This is the entire stack of the request, that in total took
>> longer than the configured time, no calls came after it.
>>
>> Stack trace gist: https://gist.github.com/Dynom/156e5fa1217ce527dd39
>>
>>
>> Thanks for reading.
>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "highload-php-en" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to highload-php-en+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "highload-php-en" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to highload-php-en+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



--
MVG,
Mark van der Velden

--

---
You received this message because you are subscribed to the Google Groups "highload-php-en" group.
To unsubscribe from this group and stop receiving emails from it, send an email to highload-php-en+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 55
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready