Search before asking
Description
Optimization Description
The /api/catalogue/getCatalogueTreeData interface loads very slowly when there are a large number of catalogue and job records.
In our actual production scenario, we have about 1500 jobs and dozens of directories, with a maximum directory depth of 3 levels. Currently, the tree loading response time takes more than 28 seconds, which seriously affects user experience.
Current Problem
The catalogue tree uses full data loading. All directory and job data is queried and parsed at once, resulting in excessive interface response time when the data volume increases.
Expected Optimization
Optimize the catalogue tree loading logic. Support lazy loading of tree nodes or optimize database query efficiency to reduce interface response time.
Environment
- Dinky version: 1.2.3/1.2.4/1.2.5
- Database: MySQL
Are you willing to submit a PR?
Code of Conduct
Search before asking
Description
Optimization Description
The /api/catalogue/getCatalogueTreeData interface loads very slowly when there are a large number of catalogue and job records.
In our actual production scenario, we have about 1500 jobs and dozens of directories, with a maximum directory depth of 3 levels. Currently, the tree loading response time takes more than 28 seconds, which seriously affects user experience.
Current Problem
The catalogue tree uses full data loading. All directory and job data is queried and parsed at once, resulting in excessive interface response time when the data volume increases.
Expected Optimization
Optimize the catalogue tree loading logic. Support lazy loading of tree nodes or optimize database query efficiency to reduce interface response time.
Environment
Are you willing to submit a PR?
Code of Conduct