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

James Peach commented on TS-4924:
---------------------------------

See {{HttpTransact::initialize_state_variables_from_request}} where we always 
disable keepalive for internal requests. This means that any protocol plugin 
will have keepalive disabled. {{wrk}} is extremely aggressive about using 
keepalive (always sends all requests on keepalive), so the non-protocol plugin 
results are unrealistically high.

> Protocol plugin performance penalty
> -----------------------------------
>
>                 Key: TS-4924
>                 URL: https://issues.apache.org/jira/browse/TS-4924
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Performance, Plugins
>            Reporter: James Peach
>             Fix For: sometime
>
>
> It looks like protocol plugins take a significant performance penalty 
> compared to doing the same work in the code.
> *Configuratation:*
> {noformat}
> [root@fedora-23 ~]# cat /opt/ats/etc/trafficserver/remap.config
> map http://generator.jpeach.org/ http://127.0.0.1/ \
>       @plugin=generator.so
> [root@fedora-23 ~]# cat /opt/ats/etc/trafficserver/plugin.config
> passthru.so
> [root@fedora-23 ~]# tail /opt/ats/etc/trafficserver/records.config
> ...
> CONFIG config.plugin.passthru.server_ports STRING 9090
> {noformat}
> *http_load:*
> {noformat}
> http://generator.jpeach.org/cache/1024/1934f6c8-2cd6-46ea-9077-0532528fb1c9
> [vagrant@fedora-23 ~]$ http_load -proxy 127.0.0.1:8080 -parallel 50 -seconds 
> 20 -keep_alive 4 url.lst
> {noformat}
> We are using a generator URL of 1K that gets served from cache.



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

Reply via email to