[jira] [Commented] (TS-1893) Make ATS use keep-alive connections per origin address

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

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

Leif Hedstrom commented on TS-1893:
-----------------------------------

So, I like this idea, and looking at it, it should most likely be done using a new configuration option, e.g. proxy.config.http.session_sharing_hash  or some such, with at least two options (0 and 1). I understand this patch is a POC, but Tomasz, are you going to work on this? I think it needs to be done in a way such that we eliminate the 2nd hash bucket entirely when the configuration says not to use it, right?

In any case, let me know if this is something you plan on working on asap, or if we should move it out to post-3.4.0 release. I can also imagine that this is something e.g. GoDaddy would be very interested in.
                
> Make ATS use keep-alive connections per origin address
> ------------------------------------------------------
>
>                 Key: TS-1893
>                 URL: https://issues.apache.org/jira/browse/TS-1893
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: HTTP, Network, Performance
>            Reporter: Tomasz Kuzemko
>            Assignee: Leif Hedstrom
>             Fix For: 3.3.3
>
>         Attachments: TS-1893-PoC.diff
>
>
> In current implementation Traffic Server uses a two level hash for keep-alive connections: server ip -> hostname -> keep-alive session.
> The reasoning behind this was that some old http servers could not handle the request properly for different virtual hosts on the same keep-alive session. Recent web servers should all handle this situation correctly.
> The improvement would be to make a single level hash to keep just the server ip. Shared hosting configurations using ATS as a reverse-proxy could benefit the most from this improvement.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira