Just to be clear - it works for most searches with ~300ms response times but for others (and always

*

) it takes >1000ms

q=*

is generally more time consuming since it could match the entire dataset, and then depending on the sort parameters, the entire dataset potentially needs to be then sorted... But hard to tell the exact issue without the dataset, query patterns, etc. We only offer this level of performance debugging on Typesense Cloud though

@Jason Bosco thanks! Wasn't looking for someone to do the debugging, but just some pointers on what to look at. I'll try removing the sort (we do indeed have a default sorting field) ✌️ It is on Typesense Cloud but I'm going to assume that it requires a dedicated support subscription to get that kind of debugging help 😜

Oh if it's on Typesense Cloud, I can see if there are any quick improvements that can be done with the query structure, even without a support plan. (Where a support plan would be required is if we need to add some dataset specific optimizations for eg) Could you DM me a full curl request that replicates the issue?