MockServer enables easy mocking of any system you integrate with via HTTP or HTTPS with clients written in Java, JavaScript and Ruby. MockServer also includes a proxy that introspects all proxied traffic including encrypted SSL traffic and supports Port Forwarding, Web Proxying (i.e. HTTP proxy), HTTPS Tunneling Proxying (using HTTP CONNECT) and SOCKS Proxying (i.e. dynamic port forwarding).
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.
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.