Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEEDBACK] RuntimeManager should have a connection pool instead of a connection per request. #203

Open
AlmogBaku opened this issue Dec 1, 2022 · 0 comments
Open

[FEEDBACK] RuntimeManager should have a connection pool instead of a connection per request. #203

AlmogBaku opened this issue Dec 1, 2022 · 0 comments
Labels
component/runtime-sidecar Related to the Runtime-sidecar enhancement New feature or request roadmap This issue is part of the roadmap

Comments

@AlmogBaku
Copy link
Member

Background

Currently, the runtimemanager is creating a new connection per request. This is not very efficient and performant.

What do you propose to do?

We should create a connection pool per runtime environment and reuse these connections.

What have you already tried?

No response

What else should we know?

No response
@AlmogBaku AlmogBaku added enhancement New feature or request component/runtime-sidecar Related to the Runtime-sidecar labels Dec 1, 2022
@AlmogBaku AlmogBaku added the roadmap This issue is part of the roadmap label Jan 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/runtime-sidecar Related to the Runtime-sidecar enhancement New feature or request roadmap This issue is part of the roadmap
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@AlmogBaku