-
Notifications
You must be signed in to change notification settings - Fork 148
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
Expose an API to close channels #769
Comments
@bcoe / @BenWhitehead / @JustinBeckwith Thoughts? I am not opposed, especially since we now offer |
No concerns from me, but I defer to @bcoe and @BenWhitehead |
Sounds like a good thing to me, this also already exists in the Java server sdk via ( |
@schmidt-sebastian, @BenWhitehead we should loop in @alexander-fenster to this conversation too 😄; there was conversation about functionality along the lines of |
Thanks for picking it up @schmidt-sebastian! We're also doing some work to make it actually work with |
We are currently stuck trying to get the new Typescript generator to play nicely with the repo, but hope to have this resolved early next week. If you are blocked by this, I am not opposed to applying the changes manually to |
Hey, thank you for the update, much appreciated. One more week of oversized VMs won’t kill anyone, so take your time 🙂 |
@schmidt-sebastian Is it now unblocked with changes made in v3? 😃 |
Yes! @thebrianchen will take care of this. |
@thebrianchen @schmidt-sebastian Thank you so much! Feels like I got my Christmas gifts early 😄 On a more scientific side, I reduced my socket usage by 96.875% and memory usage by 1.4 GBs per thread! |
Is your feature request related to a problem? Please describe.
Running more than one instance of Firestore in isolated, disposable contexts is not possible, as the underlying connection makes it impossible for these clients to be cleared from memory.
An example would be to use Node.js VM.
Describe the solution you'd like
I'd like to see an API to close all open streams, so the client can be garbage collected.
Describe alternatives you've considered
Hacking my way into
@grpc/grpc-js
, which exposes this API.Additional context
Here's an example of what it can cause :)
The text was updated successfully, but these errors were encountered: