Hi,
I've done some performance tests with API Gateway 9.2.
Some parameters were tuned well I think.
The result of the tests was good enough. As expected, HTTP was twice as good as HTTPS, (simply http 4000 tps vs https 2000 tps )
But, there is a odd thing during the tests. When we test with HTTPS, we've got some errors all the time in JMeter(actually BlazeMeter). There is no error with HTTP.
Is there specific tuning parameters for HTTPS processing?
Or, Any idea what could be the reason for this?
Non HTTP response code: java.net.SocketException | Non HTTP response message: Connection reset |
Non HTTP response code: java.net.SocketTimeoutException | Non HTTP response message: connect timed out |
Non HTTP response code: java.net.SocketTimeoutException | Non HTTP response message: Read timed out |
The errors rate is under 0.2%. (We could ignore these errors, but have to explain)
There is no LB between JMeter and API Gateway node.
JMeter VUser 2000
io.httpCoreConcurrency 2000
io.httpMaxConcurrency 2500
io.httpConnectionIdleTimeout 5
c3p0DataSource.maxPoolSize 2650
com.l7tech.common.http.prov.apache.CommonsHttpClient.maxConnectionsPerHost=50000
com.l7tech.common.http.prov.apache.CommonsHttpClient.maxTotalConnections=100000
com.l7tech.server.policy.assertion.ServerHttpRoutingAssertion.statePool.enable=true
... (and irrelevant params)
note : I've got the same errors when we double them(concurrency).
Regards
Becky