performance regression for filter evaluation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
there has been a regression in filter evaluation performance since https://github.com/mapbox/mapbox-gl-js/pull/5665 – we accepted an initial performance hit (~0.2ms -> ~0.6ms) as part of eliminating `unsafe-eval` requirement, but there seems to have been further degradation since that change.
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 reviewing pull request #5665 and the linked performance image to understand the accepted baseline and the later regression. Locate the current filter-evaluation path and establish a repeatable performance comparison; done means identifying the source of the additional degradation and confirming the evaluation time no longer exceeds the intended baseline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100