#community-help

Tradeoffs of Searching Within Multiple Geo-Polygons vs One Superset

TLDR Ivy asked about tradeoffs in searching within multiple geo-polygons vs one "superset". Kishore Nallan explained that additional filters take more time, but the impact depends on data size and query scope.

7mo

Join the chat

Apr 26, 2023 (7 months ago)

Photo of md5-2f39998c05c5409f8c3521187ec34d4e

Ivy

08:21 PM

Hi everyone! What are the tradeoffs of searching within multiple geo-polygon vs one "superset" geo-polygon? I'm mainly curious if there is a big latency hit with adding additional OR filters

Apr 27, 2023 (7 months ago)

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

12:43 AM

Each filter clause is an additional filter operation so will take additional time. Actual impact will depend on size of data and scope of query.

Ivy

02:40 PM

Thank you!

Typesense

Lightning-fast, open source search engine for everyone | Knowledge Base powered by Struct.AI

Indexed 3005 threads (79% resolved)

Join Our Community

Similar Threads

Searching for Polygons within a Polygon in Geo-search

Stefan inquired about searching polygons within polygons. Jason referred to a GitHub issue, but Stefan later realized the current behavior suffices.

8mo

Using TypeSense for Geolocation Tagged Job Search

Nicholas needed help to enable geo-location based job search on a board. James suggested using filter_by from TypeSense, while Jason elaborated on 'OR' and 'AND' operations in TypeSense.

27mo

Optimizing Bulk Indexing and Reducing RAM Usage in Typesense

Timon experienced issues with Typesense becoming unresponsive during bulk indexing and sought advice. Jason recommended larger import requests and adjusting the client-side timeout allowance, revealing a need to increase RAM allocation for Docker. Kishore Nallan undertook to find ways to optimize memory usage, particularly for geopoint indexing.

24mo