Add query benchmark module and performance docs page #336
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was inspired to write this up after seeing how well titiler-pgstac can perform with high resolution global datasets in collections with massive STAC item footprints (check out this demo). In contrast, collections with many tiny (<100 km squares) do not perform as well because the query time for low zoom tile (z<=5) searches is too long for titiler-pgstac (check out this demo).
It is not strictly a
pgstac
problem but the goal is to provide some food for thought topgstac
users who get to choose the size of their STAC items/assets but don't have much context for why any size is good/bad.