CPU Perf Issues (pointclouds)
- Dominant language
- JavaScript
- Stars
- 15.7k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
Just documenting current CPU perf issues in cesium (pointclouds).
Built with combineRelease.
Biggest and most consistent bottleneck: loading the whole payload when it comes back. Already on a promise so maybe not such a big deal (not blocking main thread, not leading to camera stutter on flight)
Thinner call stacks are the normal render, wider call stacks are the payload loading (zoomed out of above)
Not as common but a few of these (bufferData from createVertexBuffer)
Non-image related issues mentioned in #7400 affect pointclouds as well.
One additional thing that seems unique to pointclouds is View.createPotentiallyVisibleTileset. (Or at least noticeable relative to its typical render time). Consistently around 5ms. Related to many calls to ShaderCache.getDerivedShaderProgram
Contributor guide
Research direction
Start by reproducing the point-cloud CPU profiles with a combineRelease build, focusing on payload loading, bufferData from createVertexBuffer, and View.createPotentiallyVisibleTileset with ShaderCache.getDerivedShaderProgram. The issue documents bottlenecks but does not define a code change, performance target, or acceptance criteria, so completion would require scoping those first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100