You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for this great extension! It is one of the basic extensions in our system-wide JupyterLab installation on multiple clusters and we love it :) Because of that I have very high interest that the following issue is known.
jupyter-resource-usage sets enable_prometheus_metrics = True by default.
But this has a huge impact on the whole JupyterLab installation:
At the moment jupyter-resource-usage is overloading tornado's task-pool for the prometheus- (and the cpuload- feature (?) ) without taking into account that this will result in less (or even worst) performance for the critical webserver.
We had a big issue with our server-proxies started via jupyter-server-proxy as we saw a significant performance degradation which was extremely time consuming to track down in a complex cloud environment. The remote desktop integration Xpra was showing stuttering effects ( jupyterhub/jupyter-server-proxy#494 ) and the robustness of web socket connections in general were affected at multiple places.
We were looking in all directions (NGINX, JupyterHub, Kubernetes, OpenStack, Network, JupyterLab, jupyter-server-proxy, etc) but unfortunately the last we had in mind was jupyter-resource-usage.
We are fine now as we have changed our jupyter-resource-usage's config of course. But other users will stumble over the issue in the same way.
This problem has already been discussed in the past here: #123 and an opt-out functionality was implemented here dleen@8c5d477 .
=> I would suggest to change that to an opt-in.
The text was updated successfully, but these errors were encountered:
This problem has already been discussed in the past here: #123 and an opt-out functionality was implemented here dleen@8c5d477 .
If you feel like opening a PR with this change, that would be great.
At first glance it would indeed make sense to change the default. But since some users may expect the current default, maybe this would have to be released in a 2.0.0 version (unless there are some points for considering this as a minor change).
Thank you for this great extension! It is one of the basic extensions in our system-wide JupyterLab installation on multiple clusters and we love it :) Because of that I have very high interest that the following issue is known.
jupyter-resource-usage
setsenable_prometheus_metrics = True
by default.But this has a huge impact on the whole JupyterLab installation:
At the moment
jupyter-resource-usage
is overloadingtornado
's task-pool for the prometheus- (and the cpuload- feature (?) ) without taking into account that this will result in less (or even worst) performance for the critical webserver.We had a big issue with our server-proxies started via
jupyter-server-proxy
as we saw a significant performance degradation which was extremely time consuming to track down in a complex cloud environment. The remote desktop integration Xpra was showing stuttering effects ( jupyterhub/jupyter-server-proxy#494 ) and the robustness of web socket connections in general were affected at multiple places.We were looking in all directions (NGINX, JupyterHub, Kubernetes, OpenStack, Network, JupyterLab, jupyter-server-proxy, etc) but unfortunately the last we had in mind was
jupyter-resource-usage
.We are fine now as we have changed our jupyter-resource-usage's config of course. But other users will stumble over the issue in the same way.
This problem has already been discussed in the past here: #123 and an
opt-out
functionality was implemented here dleen@8c5d477 .=> I would suggest to change that to an
opt-in
.The text was updated successfully, but these errors were encountered: