Leaflet / Leaflet/Leaflet.VectorGrid
High CPU usage on Vector Tile Layers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 676
- Forks
- 202
- PR merge metrics
- No merged PRs in 30d
Description
Hi there, I'm using vector grid with leaflet 1.0, thing is when the layer start to draw vector tile serve from geoserver or any other provider, CPU usage goes way up to 100% on chrome, it even freezes, I'm trying to draw near to 37k points with nothing more than the default options on the layer, I also include rendererFactory: L.canvas.tile and interactive:true, I'm using the bundle package, any idea why this could by happening, thanks in advance
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
Reproduce the freeze in Chrome with Leaflet 1.0, a vector tile layer containing about 37k points, and the reported bundle and rendererFactory options. Compare behavior with interactive enabled and disabled, then identify a measurable change that prevents CPU usage from reaching 100% and the browser from freezing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100