-
Notifications
You must be signed in to change notification settings - Fork 505
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
Memory issue #209
Comments
It might be that the kernels are not properly beeing shut down upon refresh / closing of browser tabs. We might need to implement an automatic shutdown in case of inactivity in jupyter_server. |
Yeah, I am thinking about making a hack cron job with |
@scottlittle you can use the traitlets configuration system to specify how often kernels are culled, so they can be terminated when they are not active anymore. For example: voila --MappingKernelManager.cull_interval=10 --MappingKernelManager.cull_idle_timeout=10 example.ipynb Or create c.MappingKernelManager.cull_interval = 10
c.MappingKernelManager.cull_idle_timeout = 10 Related to #55. |
Which version of voila were you using? After 0.10, this may happen less often since the browser now triggers the shutdown of kernels (till 0.10 there was an issue with that for chrome). And otherwise what @jtpio says seems the best option. |
@maartenbreddels I'm using |
@jtpio I created |
These are actually threads of the initial process (process 1217 in my case, as seen when running |
Here's my output to
|
@scottlittle would you mind trying the same but with the classic notebook server? That means placing the |
@jtpio I set the cull settings in |
@scottlittle by that I meant starting the notebook server with This should pick up the cull settings. |
@jtpio got it. After opening, running, and closing some apps and letting them be culled, this is what I got (see Jupyter processes at bottom):
I didn't shutdown the voila before doing this, and you can see that the problem persists there. |
I'm running into memory issues while running voila. It seems like old processes hang around and slowly increase the memory until almost complete unresponsiveness and I need to reboot. I am using a fresh install of Ubuntu 18.04 on AWS, pip3 install everything, and redirect port 8866 to 80 using iptables. Here's a screenshot of
htop
:I'm unable to sort by anything at this point due to unresponsiveness. I was wondering if anyone has experienced anything similar and what they have done about it.
TLDR; After launching voila, I have a bunch of zombie processes eating my memory until I have to reboot.
The text was updated successfully, but these errors were encountered: