#kernel-launch

Latency spikes during concurrent notebook launches in default server configuration

The Jupyter Notebook server handles HTTP and WebSocket traffic through a single Tornado I/O loop, and latency can surface only when multiple clients request notebooks or kernels concurrently rather than during isolated sessions. The default deployment runs a single worker process, and each kernel launch spawns a separate Python process whose overhead is not