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
After I enabled track_cpu_percent for the JupyterHub users I support, we noticed a significant regression in the input delay of the JupyterLab integrated terminal. I made a screen recording that demonstrates the frequent lags we are seeing in displaying what the user is typing, even when typing at a modest but steady rate:
Screen.Recording.2025-03-21.at.9.07.48.AM.mov
When track_cpu_percent is disabled, the input delay is restored to an acceptable level:
Screen.Recording.2025-03-21.at.9.11.02.AM.mov
Reproduce
Enable track_cpu_percent
Open the integrated terminal
Type at a moderate, steady rate
Notice frequent lags in displaying what you typed
Disable track_cpu_percent
Notice the lag is much better
Context
Operating System and version: Observed on macOS Sequoia, Windows 11, and Linux (various versions)
Browser and version: Observed on Chrome and Edge
Jupyter Server version: 2.15.0
jupyter-resource-usage version: 1.1.1 (latest as of today, 3/21/25)
[I 2025-03-21 13:21:42.757 ServerApp] jupyter_resource_usage | extension was successfully loaded.
which does not differ between enabling and disabling `track_cpu_percent`
Browser Output
Does not differ between enabling and disabling `track_cpu_percent`
The text was updated successfully, but these errors were encountered:
Meant to say, text input in notebooks and in text editor tabs is not affected. The severe input lag has only been observed in the integrated terminal thus far.
Description
After I enabled
track_cpu_percent
for the JupyterHub users I support, we noticed a significant regression in the input delay of the JupyterLab integrated terminal. I made a screen recording that demonstrates the frequent lags we are seeing in displaying what the user is typing, even when typing at a modest but steady rate:Screen.Recording.2025-03-21.at.9.07.48.AM.mov
When
track_cpu_percent
is disabled, the input delay is restored to an acceptable level:Screen.Recording.2025-03-21.at.9.11.02.AM.mov
Reproduce
track_cpu_percent
track_cpu_percent
Context
Troubleshoot Output
Command Line Output
Only relevant output is which does not differ between enabling and disabling `track_cpu_percent`Browser Output
Does not differ between enabling and disabling `track_cpu_percent`The text was updated successfully, but these errors were encountered: