Lots of models leads to high GC usage
Open
category - memory/performance
category - model/gltf
onramping
priority - high
type - enhancement
- Dominant language
- JavaScript
- Stars
- 15.8k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
As discussed here: https://github.com/AnalyticalGraphicsInc/cesium/pull/3059#issuecomment-150645643
This could be true for all primitives (meaning the issue is in `Scene.render`, not `Model.update`). @lilleyse is looking into it.
Contributor guide
Research direction
Review the linked discussion and compare the rendering path in Scene.render with the model-specific path in Model.update. Reproduce the high-GC-usage case with many models, then use that scenario to identify which path accounts for the excess collection. Done means the model-heavy case no longer produces unexpectedly high GC usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- computer-graphics, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100