CPU Perf Issues (Terrain and Imagery)
- 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 (terrain and imagery).
Built with combineRelease.
Read pixels can take a while, not sure if that can be helped:
Compiling the shader ahead of time might help or at least compiling it before it's needed (unless of course that's what it's trying to do here):
Or maybe try what's mentioned here for non-blocking shading compilation:
http://toji.github.io/shader-perf/
Contributor guide
Research direction
Reproduce the terrain and imagery workload using a combineRelease build, then review the readPixels and shader-compilation traces shown in the issue. Compare the observed behavior with the non-blocking shader compilation approach linked in the report. Done means identifying a concrete CPU bottleneck and validating an improvement against the reported traces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics, performance, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100