On May 13, 2013, at 7:12 AM, Tomasz Kuzemko <[email protected]> wrote:
> Hello, > > I'm running ATS in front of a fairly large *shared* webserver (many vhosts). > I've noticed that with keep-alive Traffic Server keeps a two level hash of > established sessions: ip -> hostname -> session. Because of this ATS opens > way too many connections than are needed. > > In HttpSessionManager.cc I found this comment which explains the reasoning > behind this: > > // We compute the mmh for matching the hostname as the last > // check for a match between the session the HttpSM is looking > // for and the sessions we have. We have to use the hostname > // as part of the match because some stupid servers can't > // handle getting request for different virtual hosts over > // the same keep-alive session (INKqa05429). > > Do you know which servers were affected by such bug? > > I made a small patch to disable the 2nd level hash and noticed a huge > performance benefit under heavy load. Would it be possible to have this as an > option in records.config? I don't see any issues with having this as an option. If you file a bug at https://issues.apache.org/jira/browse/TS and attach your patch, I'll review and merge it cheers, James
