-
Notifications
You must be signed in to change notification settings - Fork 467
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
Slow performance with imports in some cases #29162
Comments
Let's test how this branch coursesCT-01J6DJJG7W1DC6NKJX8A7SNTV6.tar.gz It shouldn't throw a Java heap. |
Tested Locally with -Xmx1G. Master threw the following error before throwing the error imported 470 Courses:
Branch imported 953 contentlets in 7 minutes and 6 seconds. (This is ok since the CSV has dupe courses).
|
This does a few things: - Removes reading the file in as a byte[] and instead passes around a `File` object - Changes how the import is run inline (helpful for glowroot traces) or to use the DotSubmitter thread pool. Config var is `IMPORT_CONTENTLETS_ASYNC` - Commit Granularity changed to 100, meaning every 100 contentlets will be committed and a new transaction will be started. - Copied CSV file to tmp dir. ref: #29162 --------- Co-authored-by: erickgonzalez <[email protected]>
Passed internal QATested in demo, the import process lasted 7 minutes and 2 seconds
|
Approved: Tested on trunk_5b70657, Docker, macOS 14.5, FF v126.0.1 Import took less than a minute to complete. |
Parent Issue
No response
Problem Statement
We have seen some cases where importing content can take a long time. Additionally, when importing content, it spins up a new thread, which does not report to glowroot, making identifying these issues difficult. We need to optimize for this.
Steps to Reproduce
Create a content type with 20 fields. Run a csv import of a large amount of records for that type with glowroot attached to the dotCMS
There will be no glowroot reporting/traces to help identify slow code.
Acceptance Criteria
We can add some blind fixes here but the real test will be if we can get the import to work nicely in an environment that is sized down.
dotCMS Version
24.05
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
The text was updated successfully, but these errors were encountered: