NASA-AMMOS / NASA-AMMOS/3DTilesRendererJS
TilesRenderer: Handle unloading internal tile sets more intelligently when reaching the memory cap
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.5k
- Forks
- 416
- Avg merge
- 17h 52m
- Merged PRs (30d)
- 37
Description
Currently internal tile sets are modeled has having "0" bytes but it may be possible for them to still be removed when our memory cap is reached. Internal tile sets are usually unloaded last, though, so the current behavior should be validated first.
Contributor guide
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
The issue names no files or tests. Start by tracing the memory-cap eviction path and internal tile-set handling; first validate whether zero-byte internal sets are currently unloaded last. Done means the intended behavior when the cap is reached is established and the resulting behavior is validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- computer-graphics, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100