The first thing you will need to change for such a test is the number of simultaneous connections accepted by the Apache web server: by default the max is 256. See the Apache documentation here:

In addition I also suggest that you consider using the "worker" multi-processing module instead of the "prefork", as it usually works better when talking to a Java application server, because it re-uses connections better.

On 03/07/2018 02:20 PM, Hari Prasanth Loganathan wrote:
Hi Team,

*Description of problem:*

I am trying to achieve 1000 concurrent request to oVirt. What are the
tunable parameters to achieve this?

I tried to perform the benchmarking for ovirt engine using Apache benchmark
using the same SSO token.

ab -n 1000 -c 500 -k -H "accept: application/json" -H "Authorization:

When the number of concurrent request is 500, we are getting more than 100
failures with the following error,

SSL read failed (1) - closing connection

NOTE: It is scaling for concurrent request below 500.

I used the profiler to get the memory and CPU and it seems very less,

   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+
30413 ovirt     20   0 4226664 882396   6776 S 126.0 23.0  27:48.53 java

Configuration of the machine in which Ovirt is deployed :

RAM - 4GB,
Hard disk - 100GB,
core processor - 2,
OS - Cent7.x.

In which 2GB is allocated to oVirt.

Version-Release number of selected component (if applicable):


How reproducible:

If the number of concurrent requests are above 500, we are easily facing
this issue.

*Actual results:*

SSL read failed (1) - closing connection

*Expected results:*

Request success.


Users mailing list

Users mailing list

Reply via email to