Test JupyterLab with many extensions

[jtpio]

Problem

It would be interesting to set up some basic tests to see how the number of installed extensions could impact the loading time of the JupyterLab application.

For example does the loading time grow linearly with the number of installed extensions?

Proposed Solution

Set up a (recurring?) job that would pull the latest JupyterLab stable (or dev) version and install a given number of extensions (for example 10 or 100). And measure the time it takes for the splash animation to disappear.

Additional context

This can be relevant for large organizations and JupyterLab deployments that include many third-party extensions.

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[krassowski]

I guess to make it maintainable, this should probably use some kind of a dummy-auto generated extension. Maybe we could generate a number of extensions from extension-template for this.