You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: