Connection Pooling

Reuse TCP connections with
HTTP/2 multiplexing

Keep TCP connections alive and reuse them for requests to the same host. Combined with HTTP/2 multiplexing, dramatically reduce connection overhead and improve performance for parallel requests.

View DocumentationDownload curl-runner

Enable connection pooling with HTTP/2 multiplexing

connection-pooling.yaml
global:
  execution: parallel
  connectionPool:
    enabled: true
    maxStreamsPerHost: 10
    keepaliveTime: 60
    connectTimeout: 30

requests:
  - name: Get Users
    url: https://api.example.com/users
  - name: Get Posts
    url: https://api.example.com/posts
  - name: Get Comments
    url: https://api.example.com/comments
  # All 3 requests share ONE TCP + TLS connection!
Key Benefits

Why use Connection Pooling?

Single TCP Handshake

Establish one TCP connection per host instead of N connections, eliminating redundant handshakes.

Single TLS Negotiation

Perform TLS handshake once per host, saving significant time on HTTPS requests.

HTTP/2 Stream Multiplexing

Multiplex multiple requests as streams over a single connection for maximum throughput.

Use Cases

Perfect for these scenarios

High-volume API testing with reduced latency
Parallel requests to the same host
Performance-critical test suites
Load testing with connection reuse

Ready to try Connection Pooling?

Get started with curl-runner and unlock powerful connection pooling capabilities for your API testing workflow.

Install NowView on GitHub