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

QUESTION: How can rtree.index.Index properties be used to tweak performance ? #267

Open
manuel-koch opened this issue Jul 7, 2023 · 2 comments

Comments

@manuel-koch
Copy link

Looking at the docstring of Property it is not clear to me what properties can be used to tweak the performance of the index for individual use cases.

Is it possible to enhance the descriptions of the properties to give hints what values can be used to adapt to certain scenarios:

  • when using many differently sized AABBs
  • when using mostly equal sized AABBs
  • when most of the AABBs are clustered at a special region within the whole Index

E.g. I would like to know details ( typical values, range of values, use cases for values ) about properties like :

  • fill_factor
  • leaf_capacity
  • near_minimum_overlap_factor
  • reinsert_factor
  • split_distribution_factor
  • tight_mbr
  • variant, what are the differences between RT_Linear, RT_Quadratic, and RT_Star

Thank you for providing this library !

@hobu
Copy link
Member

hobu commented Jul 7, 2023

These of course all point into https://github.com/libspatialindex/libspatialindex/. Some more description about these properties can be found in the source code there, but it certainly isn't going to be the comprehensive documentation you're seeking.

I don't have much to offer in terms of guidance other than to cook up some simulations and permute parameters to see their effect.

@manuel-koch
Copy link
Author

overview.rst, RTree.h
gives very limited hints.

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

2 participants