[ 
https://issues.apache.org/jira/browse/THRIFT-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jake Farrell updated THRIFT-669:
--------------------------------

    Component/s: Java - Library

> Use Http chunk encoding to do full duplex transfer in a single post
> -------------------------------------------------------------------
>
>                 Key: THRIFT-669
>                 URL: https://issues.apache.org/jira/browse/THRIFT-669
>             Project: Thrift
>          Issue Type: Bug
>          Components: Java - Library
>    Affects Versions: 0.2
>            Reporter: Aron Sogor
>         Attachments: TFullDuplexHttpClient.java
>
>
> Instead of each method call being a separate post, use chunk-encoded request. 
> If you look at the traffic in wireshark many times the payload is much 
> smaller than the HTTP header. Using chunk encoding, the per method overhead 
> of the http header is gone. Running a simple test of getting a time as i32, 
> using http post vs chunk encoding I got from 100+ms to ~40ms per request as 
> the servlet container did not have to process the overhead of a "new request".
> More I think with jetty and continuation the long running connections could 
> actually scale and perform a lot better than the current HttpClient.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to