Skip to content
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

🐛 Bug Report: Performance Issues in GitLab Plugin for Large-Scale Products. #650

Open
belurepavan71 opened this issue Nov 28, 2024 · 2 comments

Comments

@belurepavan71
Copy link

belurepavan71 commented Nov 28, 2024

📜 Description:

We have a large-scale product with a significant user base, and we've observed that the GitLab plugin's UI loading performance is severely impacted. Upon investigation, we found that duplicate API calls are being made, which could be contributing to the slow loading experience

Our large-scale product, which serves a substantial user base, is experiencing significant performance issues while using the GitLab plugin. The plugin's loading time is particularly slow, negatively impacting the user experience.

👍 Expected Behavior

  • The plugin should load quickly and efficiently, even in environments with extensive data and high user activity.
  • The plugin should send unique API calls, reducing redundancy to improve overall performance and loading times.

👎 Actual Behavior

  • The plugin takes considerable time to load when users interact with it.

Example:

  • When accessing a specific page in the GitLab plugin, users report delays.

👟 Reproduction Steps

  • Access the GitLab plugin page.
  • Note the extended time taken to load the UI and fetch data.
  • Review browser developer tools for potential performance bottlenecks.
@antoniomuso
Copy link
Contributor

Hi, @belurepavan71, sorry for the late response. Thank you for reporting it. We will fix it as soon as possible.

@belurepavan71
Copy link
Author

@antoniomuso Do we have any timeline for the above issue. It would be helpful to know when this improvement can be planned and prioritized accordingly.

Looking forward to your update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants