#community-help

Query on Performance with Many Fields in Typesense

TLDR John asked about the performance implications of having many fields but only searching on a few in Typesense. Kishore Nallan clarified that all indices are field level and independent.

15mo

Join the chat

Sep 23, 2022 (15 months ago)

Photo of md5-21545f1facb7836c149bc4c70752bd2b

John

10:56 AM

Maybe weird question but I’m curious about the performance implications of having a lot of fields but not searching/filtering/faceting on all of them. For example, you have some normal text fields and then 500 fields where you would only search/filter/facet with one of them at a time. This could be the case for an e-commerce store where the stock status depends on the warehouse, but you don’t want to keep 500 almost entirely duplicate search indices.

10:56

John

10:56 AM

Inituitively I feel like it should be OK, but I know very little about Typesense internals so 😅
(I could of course try this as well but figured someone might already know)

Photo of md5-4e872368b2b2668460205b409e95c2ea

Kishore Nallan

11:00 AM

All indices are at a field level. So they are independent.

John

11:09 AM

Great, that’s what I thought 🙂 Thanks

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

Performance Issues with Typesense Faceting and Nested Fields

Stefan experiences performance issues when faceting against 23 fields in Typesense, especially with nested fields. Kishore Nallan is working on a solution and will follow up on the thread.

9mo

Multiple Filters and JSON Requests in Typesense

Manish asked about multiple filter_by arguments, JSON input, and using multisearch. Jason offered typesense documentation links, examples, and how to use JSON formatted requests with multisearch. Ed shared a similar use case.

5mo

Discussing Document Indexing Speeds and Typesense Features

Thomas asks about the speed of indexing and associated factors. The conversation reveals that larger batch sizes and NVMe disk usage can improve speed, but the index size is limited by RAM. Jason shares plans on supporting nested fields, and they explore a solution for products in multiple categories and catalogs.

23mo