3 ms·
The load test would call kong which would proxy each request to the service being tested. Kong would be configured with the http-log plugin where performance da
by gengstrand 8y ago
The load test would call kong which would proxy each request to the service being tested. Kong would be configured with the http-log plugin where performance data would get sent to another service that would collect that data then update elasticsearch in bulk.
Last August, I tested the Dropwizard service with this setup which recorded about 20,000 RPM on GKE. This year, the same setup sent about 4,000 RPM to the Dropwizard service and the http-log plugin sent only about 200 RPM to the other service.
- bungle 8y agoUh, that is a deep drop. Just thinking, could it be related to this: https://github.com/Kong/kong/commit/de4a002565a1723bff9014cb268811b96688af6b#diff-42179ec4ac8902bb7c13b1999a071e5d https://github.com/Kong/kong/commit/de4a002565a1723bff9014cb... Definitely something for us to investigate! Thank you for feedback (I'll collect this information to our backlog).