GitAuto: A performance of a page (/settings/integrations/jira) is too slow. #141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #133
Why the bug occurs
The
/settings/integrations/jira
page experiences poor performance primarily due to slow server-side responses from theget-installed-repos
API endpoints. These requests are taking unusually long (ranging from ~800 ms to over 3 seconds), which significantly delays the overall page load time. Additionally, the page loads a substantial amount of resources (3.6 MB), which further contributes to the sluggishness.How to reproduce
/settings/integrations/jira
page in the application.get-installed-repos
requests are taking over 800 ms each.ping
request also takes around 1.14 seconds, adding to the delay.How to fix
Optimize Server-Side Processing for
get-installed-repos
:get-installed-repos
endpoints to ensure they are efficient.Reduce Payload Sizes:
get-installed-repos
and remove any unnecessary fields.Improve Network Latency:
Optimize Resource Loading:
Implement Asynchronous Loading:
Monitor and Profile Performance:
/settings/integrations/jira
page using profiling tools.By implementing these fixes, the performance of the
/settings/integrations/jira
page should improve significantly, resulting in faster load times and a better user experience.Test these changes locally