[ 
https://issues.apache.org/jira/browse/TS-4612?focusedWorklogId=27330&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-27330
 ]

ASF GitHub Bot logged work on TS-4612:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Aug/16 11:42
            Start Date: 27/Aug/16 11:42
    Worklog Time Spent: 10m 
      Work Description: GitHub user oknet reopened a pull request:

    https://github.com/apache/trafficserver/pull/771

    TS-4612: Proposal: InactivityCop Optimize

    Optimize InactivityCop on a heavy load and high level concurrent connection 
system.
    
    It is set default inactivity timeout before put vc into open_list.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/oknet/trafficserver TS-4612

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafficserver/pull/771.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #771
    
----
commit b3441cfcc7dbabb22e01d437b5940f4b50f07691
Author: Oknet Xu <[email protected]>
Date:   2016-06-30T12:13:46Z

    Proposal: InactivityCop Optimize

----


Issue Time Tracking
-------------------

    Worklog Id:     (was: 27330)
    Time Spent: 3h 50m  (was: 3h 40m)

> Proposal: InactivityCop Optimize
> --------------------------------
>
>                 Key: TS-4612
>                 URL: https://issues.apache.org/jira/browse/TS-4612
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core, Network
>            Reporter: Oknet Xu
>             Fix For: sometime
>
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> By review the processing of InactivityCop::check_inactivity():
> 1. get all local vc from open_list
> 2. put them into cop_list
> 3. check every vc in cop_list if it is already timeouted
> 4. callback vc->handleEvent to close vc if it is timeout
> InactivityCop and NetHandler share one mutex.
> InactivityCop runs every second, NetHandler runs every 10ms, that means 
> Nethandler runs 100 times until next InactivityCop runs.
> if one vc has read/write in a Nethandler call, it is won't be timeout in the 
> next InactivityCop run.
> Thus, if the vc has read/write in Nethandler, we move it out of cop-list then 
> the InactivityCop runs would get better performace.



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

Reply via email to