Users import content into dotCMS all day. Doing large imports can take a long time and also take up a ton of db and processing cycles. We should take a look at the import process and try to streamline and optimize it as much as possible.
We need to set up glowroot and take a look at our import process and find/fix code hotspots where we can.
To take into account when testing:
importing a content type with relationships (specified by an es query)
importing a content type with a unique/key field
Acceptance Criteria
Show a measurable improvement in content importing speed.
Build a list of things that most strongly affect content import performance - for example, when a contentlet has a bunch of indexed fields, or when a contentlet has many relationships - that we can document for support and the customers.
Proposed Objective
Application Performance
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Parent Issue
No response
User Story
Users import content into dotCMS all day. Doing large imports can take a long time and also take up a ton of db and processing cycles. We should take a look at the import process and try to streamline and optimize it as much as possible.
We need to set up glowroot and take a look at our import process and find/fix code hotspots where we can.
To take into account when testing:
Acceptance Criteria
Proposed Objective
Application Performance
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response