Slow startup on AMI which has large Data Science image backed in about dask-labextension HOT 4 CLOSED

Using jupyterlab 4.2.4 does not really improve performance

Launching a second notebook server to a Node with this AMI will load the extension instantly (e.g. the first notebook server will take 50 seconds, the second will take .5 seconds)

from dask-labextension.

My guess is that this has very little to do with the dask-labextension project, but cc'ing @jacobtomlinson who can maybe say so with more authority

from dask-labextension.

I'd be curious to know what happens if you stop the container and start it again. Is this some kind of first-run penalty for extensions, or does it happen every load?

I'd also recommend that you head over to the Jupyter forum and ask there as they will be able to give far better guidance than we can. If they suggest it might be extension related and theres something we can do to help the feel free to report back here and we can see what can be done.

from dask-labextension.

I'd be curious to know what happens if you stop the container and start it again. Is this some kind of first-run penalty for extensions, or does it happen every load?

Big time first time penalty. Launching a second notebook server to the same Node will load the extension in .2 seconds or something. I have also noticed that the Node takes twice as long to come online as the regular karpenter AMIs (that weren't image built by us). Likely related to the performance issues we're seeing.

Appreciate the feedback, and I have actually opened up a thread on the jupyter forum already. Will go ahead and close this as this is likely a symptom of the underlying issue rather than the problem itself (but feel free to respond if anything comes to mind :) ).

https://discourse.jupyter.org/t/slow-startup-on-ami-which-has-large-data-science-image-backed-in/27369/4

from dask-labextension.