How these command line options relate to WireMock performance in context of backing some load testing?
--container-threads: The number of threads created for incoming requests. Defaults to 10.
--jetty-acceptor-threads: The number of threads Jetty uses for accepting requests.
--max-http-client-connections: Maximum connections for Http Client. Defaults to 1000.
--async-response-enabled: Enable asynchronous request processing in Jetty. Recommended when using WireMock for performance testing with delays, as it allows much more efficient use of container threads and therefore higher throughput. Defaults to false.
--async-response-threads: Set the number of asynchronous (background) response threads. Effective only with asynchronousResponseEnabled=true. Defaults to 10.
Only --async-response-enabled options is clearly documented as related to performance testing. The first two options and the last one are somehow misleading as both are referring to the number of threads for requests handling.
I would like to do some performance testing for an API gateway and I consider using WireMock to be used to mimick downstream services.
What values for these options do you suggest?