connection pooling with http/2 when multiplexing to remote http1.1/http2 server
Date: Wed, 29 May 2019 00:21:21 +0000
I am using a libcurl client to GET content using http/2 over tls from an http1.1/2 server.
I am using the multi interface.
CURLPIPE_WAIT is not set on the easy handles.
CURLMOPT_PIPELINING=MULTIPLEX on the multi handles.
With multiplexing enabled, the download throughput is always lower than without. Also, http/2 is slower than http/1.1.
Some questions:
Is this behavior expected?
Is libcurl multiplexing all my requests through a single tcp connection to server when using http/2?
Is it possible to increase the number of tcp connections to multiplex over but still cap it to a maximum without using many multi-handles? Or using many multi-handles is the right way to do this connection pooling when using http/2?
Libcurl version: 7.52.1-5+deb9u9 + some patches.
OS: Debian 9u9
-Dheeraj
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2019-05-29