Hi! I deployed the typesense server in kubernetes. Currently this instance having around 3 million records with 32 fields in schema. When we search data it takes around 3 seconds to return the output. We hosted typesense in separate node with 32gb Ram and 100gb disk space. We communicate with this server using application load balancer. Can you please let me know what could be the reason for performance lag?

Have you tried running the query directly against Typesense without using the LB? Also how many fields are you querying? All 32 fields?

Hi...when we run the query in server, we see getting result in less than 1 sec. We are querying around 20 fields on each call

Then it must be something on the k8s / load balancer layer adding additional latency. 20+ fields is also just too many. Makes no sense to query more than 4-5. If you can group fields by concatenating them into 4-5 "buckets" and the querying on them.

We tried on stand alone server too. It is taking minimum 1.5 secs now. As you mentioned, we tried to query only 5 fields. It takes more than 1.5 secs. Can you please refer some documentation for bucket concept as you mentioned in your comments?

Query times will depend on the shape of the data and specific fields queried, what kind of filter is applied, whether facets are used etc. Happy to advise if you can email support (contact@typesense.org) with more details (e.g. schema, sample query and response etc.)

We analysed and identified the issue. We are using scoped key which contains filters based on user permissions. Due to this, output takes more time. If i use admin key, then output comes much faster