influxdata / influxdata/influxdb
Find Performance Slowdown(s) In UI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
We need to narrow down the slowdowns in UI. Figure out:
1. Which components take how much bundle space?
2. Which external services/components have how much of performance hit?
3. Which API(s) cause slowdown(s), if any?
Once we have these things narrowed down, then we can tackle each of those slowdowns.
Examples of external services/components:
- Walkme
- Google Tag Manager or code injected by it
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by profiling the UI bundle and measuring the impact of the named external services, including Walkme and Google Tag Manager. Then inspect API requests for related slowdowns. Done means the relevant components, services, and APIs have measured performance impacts that can guide follow-up fixes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100