react-component / react-component/tree-select
TreeSelect with large data-set causes browser to become unresponsive
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 312
- Forks
- 204
- Avg merge
- 37m
- Merged PRs (30d)
- 1
Description
Hi there,
I'm using TreeSelect via AntD and noticed that my dataset with approx 4000 nodes was performing extremely slow when expanding/collapsing nodes and especially when searching.
When checking the Big Data example, I had a similar issue, although this managed to cause my browser to crash (in both normal and checkStrictly modes.)
The above picture shows me searching for 0-0, which after taking a screenshot and beginning to report the issue, it finally came back to life:
Browser: Chrome 59.0.3071.115 (Official Build) (64-bit) (OSX)
Available memory: 3.10gb
Is there anyway to improve performance, even in strict checking mode?
Thanks
Contributor guide
No contributing guide indexed for this repository
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 with the Big Data example and reproduce the slowdown using roughly 4,000 nodes, including search and expand/collapse in both normal and checkStrictly modes. Trace the TreeSelect paths involved in those interactions and measure whether the browser remains responsive; done means the large dataset no longer causes severe lag or crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100