Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need some extra pointers on maximizing single instance performance #1871

Open
vijayjoshi16 opened this issue May 3, 2024 · 0 comments
Open

Comments

@vijayjoshi16
Copy link

vijayjoshi16 commented May 3, 2024

Description:
I'm a backend developer. I've been utilizing a mock server extensively to facilitate testing of my backend services by returning specific dummy responses. However, I've encountered a bottleneck as I attempt to scale up my testing to handle up to 300M requests per minute.

Objective:
Before proceeding with horizontal scaling by adding multiple pods for the mock server, I aim to maximize the capacity of a single instance to handle a higher volume of requests.

Current Status:
Despite various attempts including increasing memory and CPU allocation, disabling logging, and other methods outlined in the documentation, I haven't been able to surpass 5k requests per second. Additionally, the mock server frequently experiences latency issues and SSL handshake timeouts.

I need pointers on optimizing the capabilities of a single instance before resorting to multiple pods from individuals who have successfully addressed similar challenges in the past. Any insights or recommendations on fine-tuning configurations, tweaking performance parameters, or utilizing advanced techniques to enhance the mock server's responsiveness would be greatly appreciated.

Documentation has been referenced but any shared experiences or best practices in maximizing the efficiency of mock servers in high-velocity testing scenarios outside the documentation would be invaluable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant