NASA-AMMOS / NASA-AMMOS/3DTilesRendererJS
Small optimizations: pre upload geometry, textures before rendering with them
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.5k
- Forks
- 416
- Avg merge
- 17h 52m
- Merged PRs (30d)
- 37
Description
First measure the potential performance impact of these upload times. They may be small / not worthwhile considering the size of geometry and textures in the typical tile. But this could skip the waiting on render before upload.
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
No files, tests, or entry points are identified. Start by locating the geometry and texture upload scheduling around tile rendering, then measure current upload and render-wait behavior before judging the proposed ordering. Done means recording the performance impact and determining whether pre-uploading is worthwhile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- computer-graphics, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100