[jira] [Commented] (TS-4330) Real or statistical differences in response time between 5.3 and 6.1

["Susan Hinrichs (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-4330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239756#comment-15239756 ] 

Susan Hinrichs commented on TS-4330:
------------------------------------

Some more notes.  I was seeing some OOM cores.  In other cases, the traffic_server process was being started and "out of socket memory" messages were showing up in /var/log/messages.

Looking at our memory stats, it seems that the kernel memory was being used up more than on our parallel 5.3 machine.  

Seeing similar differences with the current master build.

> Real or statistical differences in response time between 5.3 and 6.1
> --------------------------------------------------------------------
>
>                 Key: TS-4330
>                 URL: https://issues.apache.org/jira/browse/TS-4330
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Performance
>            Reporter: Susan Hinrichs
>
> We are evaluating 6.1 in our production caching environment and verifying it against a 5.3.x box in the same pod.
> Our performance reporter (ysar) shows that the response time for 6.1 is higher than it is on the 5.3 box.  The difference is in the range of 10ms.
> We also noticed that the error statistics difference.  In 6.1 the reported client aborts are higher.  Also the number of connection failures is low and the number of "other" errors is higher.  In 5.3, the number of connection failures is higher and the number of "other" errors is low.
> Finally, I set the slow log on both machines.  On the 6.1 machine, I see every second or two an entry with ua_begin set to 0, all other fields set to -1 except for sm_finish which is 120 seconds.  I do not see these slow logs on the 5.3 machine.   It is as if the TCP deferred accept path is not being used on the 6.1 build.
> We are continuing to investigate, but wanted to share in case others have seem similar issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)