Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • R rust-hello-world
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • toolforge-repostoolforge-repos
  • rust-hello-world
  • Merge requests
  • !2

Use a managed connection pool

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Legoktm requested to merge connection-pool into main Dec 23, 2022
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 3

toolforge 5.3.0 passes connection options to enable compliant connection pooling, this moves the Pool into Rocket's managed state so there is one Pool for the entire app's operation.

Tested with ab firing 20 concurrent requests but never returning an error for having too many connections, and observing that as soon as the requests ended, the connections were closed.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: connection-pool