-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Avoid creating many connection managers #25
Comments
DK318
added a commit
that referenced
this issue
Apr 1, 2022
Problem: at this moment we are creating one connection manager per `BackendEffect`. This seems ridiculous. Solution: added `Member (State (Maybe Manager))` constraint in `Sem` to store only one connection manager for all `BackendEffect` actions.
8 tasks
DK318
added a commit
that referenced
this issue
Apr 4, 2022
DK318
added a commit
that referenced
this issue
Apr 4, 2022
DK318
added a commit
that referenced
this issue
Apr 4, 2022
Problem: at this moment we are creating one connection manager per `BackendEffect`. This seems ridiculous. Solution: added `Member (State (Maybe Manager))` constraint in `Sem` to store only one connection manager for all `BackendEffect` actions.
DK318
added a commit
that referenced
this issue
Apr 4, 2022
DK318
added a commit
that referenced
this issue
Apr 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
runVaultIO
, we're creating a new connection manager on everyBackendEffect
action:This can be observed by adding a trace statement:
And then running
coffer view /
(after creating a few entries):We should refactor this so only 1 connection manager is created.
The text was updated successfully, but these errors were encountered: