Skip to content

Guzzle Pool: Performance degradation under high concurrency #13

Description

@francescobianco

Labels: performance, investigation, guzzle
Context: Bulk API requests using GuzzleHttp\Pool

Description:
When sending 100+ requests in parallel through Guzzle's Pool, Openapi SDK instantiates a new Guzzle client per request, defeating connection reuse.

Expected:
Reuse HTTP client instance and enable keep_alive option.

Impact:
Response latency increases exponentially and API rate-limits are hit sooner.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or requestguzzle

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions