performance : allow to have labels in cache
Open
- Dominant language
- TypeScript
- Stars
- 4.9k
- Forks
- 325
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 7
Description
Computing labels positions and ordering takes time for large graphs even when the number of available labels is low.
The user experience would be much improved if we had the possibility to put the result of labels computation in cache for reuse across same different displays of the same graph.
Contributor guide
Research direction
Start by locating the code that computes label positions and ordering, then inspect how separate displays of the same graph are created and whether existing caching patterns apply. Done means the label computation result can be reused across displays of the same graph and large graphs no longer repeat that work unnecessarily.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100