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

unified tile cache #128

Open
adam-ce opened this issue Oct 24, 2024 · 1 comment
Open

unified tile cache #128

adam-ce opened this issue Oct 24, 2024 · 1 comment

Comments

@adam-ce
Copy link
Member

adam-ce commented Oct 24, 2024

Currently, we have one cache per tile layer. This has the following problems

  • we will not kick out tiles of unused layers
  • inflexible resources allocation among layers, e.g. you have 16k total, but layer x is not used, so allocate 8k to y and 8k to z instead of 5k each.
  • storing the memory cache to disk creates more files (slower).

Unified tile cache:

  • tile cache has hashmap tile_type -> tile_data per tile. not all slots need to be taken.
  • query / traversal functions that only work for a certain tile type (don't descent if it is unavailable)
  • tile_type should probably be an int; the int should be chosen by registering a type via string. the registry must be stored to disk.
  • the tile cache needs synchronisation, because we likely want to use it from different threads.
@adam-ce
Copy link
Member Author

adam-ce commented Oct 24, 2024

Switch the tile querier to this unified tile cache, then this part should be good.

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

No branches or pull requests

1 participant