-
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
Documentation: serverExposureStrategy missing performance impacts #21294
Comments
@Hadsch thanks for sharing the performance impact. Indeed |
yes, devworkspaces runs only on gateway single-host. We should update the docs (I believe big docs refactorings for devworkspaces are in progress). |
@l0rd: If it is the only option since 7.42 than it would still be the question why all three options are described? |
switch to devworkspaces is big update and docs haven't catch up yet |
Perfect, then I will close the ticket now! |
Yes, big documentation refactoring / clean up is in progress #21264 |
At least on kubernetes, the setting
serverExposureStrategy
has a huge impact on the startup time of a workspace.Here you can see a comparison (credits to @sparkoo):
https://www.youtube.com/watch?v=Fhzt8DiBajU
Link to the comment: #19461 (comment)
Depending on which option you choose, the start time of a workspace can be increased or decreased by about 40 seconds.
In my opinion, this is a huge design decision that is not covered in the docs.
This is the page for the
serverExposureStrategy
:https://www.eclipse.org/che/docs/che-7/installation-guide/configuring-workspace-exposure-strategies/
Expected documentation
Performance impact for each option
Note: This might be different on MiniKube or on OpenShift. But at least for Kubernetes this setting should be considered during the setup.
The text was updated successfully, but these errors were encountered: