You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "James Peach (Commented) (JIRA)" <ji...@apache.org> on 2011/12/13 21:55:30 UTC

[jira] [Commented] (TS-912) TSFetchURL - poor performance

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

James Peach commented on TS-912:
--------------------------------

I believe that this happens when the whole response is delivered in a single event handler invocation. In this case, read_from_net() delivers the read event, but not not notice that it read to EOF and so does not deliver the EOS event. The plugin has to wait for a TCP timeout to get the EOS delivered.
                
> TSFetchURL - poor performance
> -----------------------------
>
>                 Key: TS-912
>                 URL: https://issues.apache.org/jira/browse/TS-912
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: TS API
>    Affects Versions: 3.0.0
>         Environment: Linux
>            Reporter: Naveen
>              Labels: api, perfomance, ts
>             Fix For: 3.1.2
>
>
> Running a Apache benchmark with a simple plugin that just does TSFetchURL gives a ~13ms response time. The Fetch was on a localhost. All the plugin does is just sends an "hello world" response to the client. 
> http://pastebin.com/1uEvuZqk
> Removing the TSFetchURL from the picture gives a response time of <1ms.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira