[
https://issues.apache.org/jira/browse/TS-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15176051#comment-15176051
]
Leif Hedstrom commented on TS-4244:
-----------------------------------
Sounds like maybe you are running into
proxy.config.cache.read_while_writer_retry.delay ? Or RWW in general? Or did
you fiddle with the proxy.config.http.cache.max_open_read_retries /
proxy.config.http.cache.open_read_retry_time ?
There's always going to be a tradeoff between latency, and allowing more
clients to go to origin for cache misses. You have a bunch of options here,
take a look at the "thundering heard" document on the docs.
> ATS have performance problem！
> ------------------------------
>
> Key: TS-4244
> URL: https://issues.apache.org/jira/browse/TS-4244
> Project: Traffic Server
> Issue Type: Bug
> Reporter: gehaijiang
> Fix For: sometime
>
>
> press ats meet performance problem！
> Why are some requests are processed to 50ms.
> 01/Mar/2016:11:23:47 +0800] 1 10.17.21.79 TCP_MISS/200 377 GET
> http://127.0.0.1/time.php - DIRECT/127.0.0.1 text/html
> [01/Mar/2016:11:23:47 +0800] 1 10.17.21.79 TCP_MISS/200 378 GET
> http://127.0.0.1/time.php - DIRECT/127.0.0.1 text/html
> [01/Mar/2016:11:23:47 +0800] 1 10.17.21.79 TCP_MISS/200 378 GET
> http://127.0.0.1/time.php - DIRECT/127.0.0.1 text/html
> [01/Mar/2016:11:23:47 +0800] 1 10.17.21.79 TCP_MISS/200 377 GET
> http://127.0.0.1/time.php - DIRECT/127.0.0.1 text/html
> [01/Mar/2016:11:23:47 +0800] 51 10.17.21.79 TCP_MISS/200 378 GET
> http://127.0.0.1/time.php - DIRECT/127.0.0.1 text/html
> [01/Mar/2016:11:23:47 +0800] 1 10.17.21.79 TCP_MISS/200 378 GET
> http://127.0.0.1/time.php - DIRECT/127.0.0.1 text/html
> [01/Mar/2016:11:23:47 +0800] 51 10.17.21.79 TCP_MISS/200 377 GET
> http://127.0.0.1/time.php - DIRECT/127.0.0.1 text/html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
