Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Traversal: Improve traversal performance #678

Open
gkjohnson opened this issue Aug 8, 2024 · 0 comments
Open

Traversal: Improve traversal performance #678

gkjohnson opened this issue Aug 8, 2024 · 0 comments
Milestone

Comments

@gkjohnson
Copy link
Contributor

gkjohnson commented Aug 8, 2024

Related to #669

  • Merge some of the functions. Like at least markVisibleTiles and markUsedSetLeaves.
  • Accumulate toggled tiles into a set or array so it can be iterated once rather than unnecessarily traversing through all parents.
    • Timing during tests in aerial example after load completes
      • Mark Used Tiles: ~3.1ms
      • Mark Used Set Leaves: ~0.35 ms
      • Mark Visible Tiles: ~0.1 ms
      • Toggle Tiles: ~0.25 ms
  • Lazily generate the error value & frustum state as-needed since it isn't always used.
    • Frustum state provides little to no benefit

Related goal: improve performance of loading / traversing tile set from iTowns/itowns#2335

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant