You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by Siddharth Agarwal <sa...@linkedin.com.INVALID> on 2016/09/09 17:10:44 UTC
performance problem with traffic server 6.2
Hi,
We are on the traffic server 6.2 release. We are experiencing performance
issues with this release and have enabled slow request logging. Our health
check end point sometimes is taking taking more than 3 seconds to respond.
Our CPU is idle. We are seeing most of time spent in plugin_total while
plugin_active is almost 0. Has anybody seen this issue with this release?
Some advise on how to go around debugging this?
One of the slow query logs
[Sep 8 23:25:11.006] Server {0x2ac8f230a700} ERROR: <HttpSM.cc:7125
(update_stats)> [4160091] Slow Request: client_ip: 10.133.230.32:33866 url:
http://10.133.230.41/admin status: 200 unique id: redirection_tries: 0
bytes: 5 fd: 0 client state: 0 server state: 0 ua_begin: 0.000
ua_first_read: 0.000 ua_read_header_done: 0.000 cache_open_read_begin:
-1.000 cache_open_read_end: -1.000 dns_lookup_begin: -1.000 dns_lookup_end:
-1.000 server_connect: -1.000 server_first_read: -1.000
server_read_header_done: -1.000 server_close: -1.000 ua_close: 4671.000
sm_finish: 4671.000 plugin_active: 0.000 plugin_total: 4630.000
Thanks,
Siddharth
Re: performance problem with traffic server 6.2
Posted by Alan Carroll <so...@yahoo-inc.com.INVALID>.
Based on this data the most likely explanation is a plugin that didn't call TSHttpTxnReenable().
On Friday, September 9, 2016 2:04 PM, Shu Kit Chan <ch...@gmail.com> wrote:
Is there any plugins you are using?
On Fri, Sep 9, 2016 at 10:10 AM, Siddharth Agarwal
<sa...@linkedin.com.invalid> wrote:
> Hi,
>
> We are on the traffic server 6.2 release. We are experiencing performance
> issues with this release and have enabled slow request logging. Our health
> check end point sometimes is taking taking more than 3 seconds to respond.
> Our CPU is idle. We are seeing most of time spent in plugin_total while
> plugin_active is almost 0. Has anybody seen this issue with this release?
> Some advise on how to go around debugging this?
>
>
> One of the slow query logs
>
> [Sep 8 23:25:11.006] Server {0x2ac8f230a700} ERROR: <HttpSM.cc:7125
> (update_stats)> [4160091] Slow Request: client_ip: 10.133.230.32:33866 url:
> http://10.133.230.41/admin status: 200 unique id: redirection_tries: 0
> bytes: 5 fd: 0 client state: 0 server state: 0 ua_begin: 0.000
> ua_first_read: 0.000 ua_read_header_done: 0.000 cache_open_read_begin:
> -1.000 cache_open_read_end: -1.000 dns_lookup_begin: -1.000 dns_lookup_end:
> -1.000 server_connect: -1.000 server_first_read: -1.000
> server_read_header_done: -1.000 server_close: -1.000 ua_close: 4671.000
> sm_finish: 4671.000 plugin_active: 0.000 plugin_total: 4630.000
>
> Thanks,
> Siddharth
Re: performance problem with traffic server 6.2
Posted by Siddharth Agarwal <sa...@linkedin.com.INVALID>.
Yes, we are using multiple plugins. We found the problem, one of our
plugins added a mutex to a continuation which was registered to a global
hook.
Thanks,
Siddharth
On Fri, Sep 9, 2016 at 12:04 PM, Shu Kit Chan <ch...@gmail.com> wrote:
> Is there any plugins you are using?
>
> On Fri, Sep 9, 2016 at 10:10 AM, Siddharth Agarwal
> <sa...@linkedin.com.invalid> wrote:
> > Hi,
> >
> > We are on the traffic server 6.2 release. We are experiencing performance
> > issues with this release and have enabled slow request logging. Our
> health
> > check end point sometimes is taking taking more than 3 seconds to
> respond.
> > Our CPU is idle. We are seeing most of time spent in plugin_total while
> > plugin_active is almost 0. Has anybody seen this issue with this
> release?
> > Some advise on how to go around debugging this?
> >
> >
> > One of the slow query logs
> >
> > [Sep 8 23:25:11.006] Server {0x2ac8f230a700} ERROR: <HttpSM.cc:7125
> > (update_stats)> [4160091] Slow Request: client_ip: 10.133.230.32:33866
> url:
> > http://10.133.230.41/admin status: 200 unique id: redirection_tries: 0
> > bytes: 5 fd: 0 client state: 0 server state: 0 ua_begin: 0.000
> > ua_first_read: 0.000 ua_read_header_done: 0.000 cache_open_read_begin:
> > -1.000 cache_open_read_end: -1.000 dns_lookup_begin: -1.000
> dns_lookup_end:
> > -1.000 server_connect: -1.000 server_first_read: -1.000
> > server_read_header_done: -1.000 server_close: -1.000 ua_close: 4671.000
> > sm_finish: 4671.000 plugin_active: 0.000 plugin_total: 4630.000
> >
> > Thanks,
> > Siddharth
>
Re: performance problem with traffic server 6.2
Posted by Shu Kit Chan <ch...@gmail.com>.
Is there any plugins you are using?
On Fri, Sep 9, 2016 at 10:10 AM, Siddharth Agarwal
<sa...@linkedin.com.invalid> wrote:
> Hi,
>
> We are on the traffic server 6.2 release. We are experiencing performance
> issues with this release and have enabled slow request logging. Our health
> check end point sometimes is taking taking more than 3 seconds to respond.
> Our CPU is idle. We are seeing most of time spent in plugin_total while
> plugin_active is almost 0. Has anybody seen this issue with this release?
> Some advise on how to go around debugging this?
>
>
> One of the slow query logs
>
> [Sep 8 23:25:11.006] Server {0x2ac8f230a700} ERROR: <HttpSM.cc:7125
> (update_stats)> [4160091] Slow Request: client_ip: 10.133.230.32:33866 url:
> http://10.133.230.41/admin status: 200 unique id: redirection_tries: 0
> bytes: 5 fd: 0 client state: 0 server state: 0 ua_begin: 0.000
> ua_first_read: 0.000 ua_read_header_done: 0.000 cache_open_read_begin:
> -1.000 cache_open_read_end: -1.000 dns_lookup_begin: -1.000 dns_lookup_end:
> -1.000 server_connect: -1.000 server_first_read: -1.000
> server_read_header_done: -1.000 server_close: -1.000 ua_close: 4671.000
> sm_finish: 4671.000 plugin_active: 0.000 plugin_total: 4630.000
>
> Thanks,
> Siddharth