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
Improve startup performance #23982
Labels
dotCMS : Clustering
Merged
OKR : Application Performance
Owned by Will
OKR : Cloud Engineering
Owned by Gregg
QA : Approved
QA : Passed Internal
Release : 22.03.6
Included in LTS patch release 22.03.6
Release : 23.01.2
Included in LTS patch release 23.01.2
Release : 23.05
Team : Falcon
Type : Enhancement
Comments
wezell
added
Triage
OKR : Cloud Engineering
Owned by Gregg
OKR : Application Performance
Owned by Will
dotCMS : Clustering
labels
Feb 1, 2023
wezell
added a commit
that referenced
this issue
Feb 2, 2023
wezell
added a commit
that referenced
this issue
Feb 2, 2023
wezell
added a commit
that referenced
this issue
Feb 3, 2023
PR: #24029 |
dsilvam
pushed a commit
that referenced
this issue
Mar 6, 2023
erickgonzalez
added a commit
that referenced
this issue
Mar 28, 2023
Passed Internal QA: Loading vanityURLs fast now using provided test dataset. |
Approved QA - Tested with the provided dataset |
erickgonzalez
added a commit
that referenced
this issue
May 5, 2023
erickgonzalez
added
Release : 22.03.6
Included in LTS patch release 22.03.6
and removed
Next LTS Release
labels
May 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dotCMS : Clustering
Merged
OKR : Application Performance
Owned by Will
OKR : Cloud Engineering
Owned by Gregg
QA : Approved
QA : Passed Internal
Release : 22.03.6
Included in LTS patch release 22.03.6
Release : 23.01.2
Included in LTS patch release 23.01.2
Release : 23.05
Team : Falcon
Type : Enhancement
User Story
Starting a dotCMS instance against a large scale environment can take a long time. One reason for this is that we need to load vanityUrls before we can serve content. If a customer has a lot of sites and a lot of VanityUrls, we have seen it take up to 8 minutes for dotCMS to start up and load.
Acceptance Criteria
Faster time to start.
Proposed Objective
Cloud Engineering
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
https://dotcms.slack.com/archives/CSHTYUR7H/p1675277411732569
Assumptions & Initiation Needs
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: