Hi Juan,
Thanks for the response.
I agree web server can handle only limited number of concurrent requests.
But Why it is failing with SSL handshake failure for few requests, Can't
the JBOSS wait and serve the request? We can spare the delay but not with
the request fails. So Is there a configuration in oVirt which can be tuned
to achieve this?
Thanks,
Hari
On Wed, Mar 7, 2018 at 7:05 PM, Juan Hernández <jhernand(a)redhat.com> wrote:
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:
https://httpd.apache.org/docs/2.4/mod/mpm_common.html#maxrequestworkers
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:
> Bearer SSOTOKEN"
https://172.30.56.70/ovirt-engine/
> <
https://172.30.56.70/ovirt-engine/api/vms/5440271b-afb3-48b
> b-9ff1-076fc07ebf50/statistics>
>
> 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
> 139620982339352:error:
>
> 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+
> COMMAND
> 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):
>
> 4.2.2
>
>
> 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
> 139620982339352:error:
>
> *Expected results:*
>
> Request success.
>
>
> Thanks,
> Hari
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
>
--
DISCLAIMER
The information in this e-mail is confidential and may be subject to legal
privilege. It is intended solely for the addressee. Access to this e-mail
by anyone else is unauthorized. If you have received this communication in
error, please address with the subject heading "Received in error," send to
it(a)msystechnologies.com, then delete the e-mail and destroy any copies of
it. If you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on it,
is prohibited and may be unlawful. The views, opinions, conclusions and
other information expressed in this electronic mail and any attachments are
not given or endorsed by the company unless otherwise indicated by an
authorized representative independent of this message.
MSys cannot guarantee that e-mail communications are secure or error-free,
as information could be intercepted, corrupted, amended, lost, destroyed,
arrive late or incomplete, or contain viruses, though all reasonable
precautions have been taken to ensure no viruses are present in this e-mail.
As our company cannot accept responsibility for any loss or damage arising
from the use of this e-mail or attachments we recommend that you subject
these to your virus checking procedures prior to use