projectwallace / projectwallace/css-analyzer
perf: do analysis outside of main loop
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 366
- Forks
- 15
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 3
Description
Try out if we can get a perf speedup if we separate data collection and data analysis. Collection happens in the big walker function in index.ts where we push all data to some separate containers. Analysis happens after the walker is done.
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 in index.ts and trace the big walker function to identify where data is collected and where analysis runs afterward. Profile the current single-loop approach, then compare it with separated collection and analysis; done means establishing whether the separation produces a measurable performance speedup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100