-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
20+ seconds faster Che-Theia startup #20861
Comments
I detected that we have the delay at |
@azatsarynnyy 7.41.0 release will be cut tomorrow. This issue is not yet closed, so please close it if it's done or move it to 7.42 |
I had a quite long vacation, will come back to the issue today/tomorrow... |
I detected that the system hangs on I investigated the problem using Finally, I found that we are waiting for unpacking I tried to put already unpacked Behaviour for packed start_workspace_packed_plugins.mp4Behaviour for unpacked unpacked_plugins_2.mp4 |
@l0rd actually, it's > 20 sec. faster for hosted Che instance just FYI 🙂 |
@azatsarynnyy thanks. I have updated the title and the release notes. |
sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-2712 |
Describe the bug
It takes about 10 sec. after Che-Theia is loaded to the browser and before the project tree is rendered.
Che version
next (development version)
Steps to reproduce
Start a new workspace with the following factory URL:
<che-host>#https://github.com/l0rd/spring-petclinic?devfilePath=.devfilev2.yaml
It takes about 10 sec. before the project tree is rendered. During that time the tree is empty. However, the project sources are already cloned.
Expected behavior
The projects tree should be rendered as soon as Che-Theia page is loaded to the browser.
Runtime
OpenShift
Screenshots
Installation method
OperatorHub
Environment
Linux
Release Notes Text
The previous DevWorkspace based Che-Theia used to take more than 20 seconds to load due to some blocking built-in plugins startup. The built-in plugins are not blocking the main Theia process startup anymore.
The text was updated successfully, but these errors were encountered: