Skip to content

[Optimization] Optimize Catalogue Loading Performance (Takes ~1 Minute When Catalogues Reach 2,000+) #4511

@kaijli-bigdata

Description

@kaijli-bigdata

Search before asking

  • I had searched in the issues and found no similar optimization requirement.

Description

Background

When using Dinky with a large number of catalogues (e.g., around 2,000+), the catalogue tree loading API becomes extremely slow.
In real scenarios, the API response time reaches about 1 minute, causing a long loading state on the UI and significantly affecting user experience.

Current Behavior

With 2,000+ catalogues, the catalogue loading API takes ~60 seconds to respond.

The UI remains in a loading state for an extended period.

Refreshing the page or restarting the service does not improve the performance.

Image

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions