#community-help

Improving Typesense Server Performance

TLDR Tiago reported slowed server performance due to multiple requests to typesense. Jason suggested increasing the number of CPU cores to handle greater concurrency.

17mo

Join the chat

May 15, 2022 (17 months ago)

Photo of md5-e737d4d738b6706979f35b30fc063975

Tiago

04:35 PM

Hello, I implemented typesense on the project that I am currently working.
When I’m receiving a lot of requests at the same time seems that typesense can't handle them all and the server slows down.
What do you recommend to improve the performance?

Photo of md5-8813087cccc512313602b6d9f9ece19f

Jason

06:45 PM

Concurrency is determined by the number of CPU cores you have on your machine. To support more concurrency, you'd want to add more CPU cores

Tiago

08:16 PM

Thanks Jason, I will suggest that to my team 👍

Typesense

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

Indexed 2779 threads (79% resolved)

Join Our Community Manage subscription

Similar Threads

Typesense Concurrency and Performance Concerns

arpit was concerned about concurrency issues in Typesense. Jason explained that upserts depend on CPU capacity and number of fields, and should be manageable with adequate resources.

7mo

Addressing Typesense Server Issues and Optimization Needs

Robert had an issue with a 'stuck' typesense server. Jason and Kishore Nallan gave advice on handling writes, configuration for high search volumes, and running multiple typesense instances. They also recommended monitoring CPU usage and updating the server version for bug fixes.

12mo

Troubleshooting Typesense Document Import Error

Christopher had trouble importing 2.1M documents into Typesense due to memory errors. Jason clarified the system requirements, explaining the correlation between RAM and dataset size, and ways to tackle the issue. They both also discussed database-like query options.

8mo