High Volume Testing, Identifying Break Points
#############################################

Now it is time to generate a high volume of traffic and see where the breaking points are.

|
|

1) **Run Locust test with a high volume of Users**
   
Number of Users: 2000

Spawn rate: 200

Host: http://10.1.1.9/

Advanced Options, Run time: 30s

.. image:: /class8/images/locus-2000-200-30.png  
   :width: 200 px
	
Review Locust Charts

.. note::  Any changes to the graphs?  Were there any failures?
	
If seeing failures, review the Failures tab on the top row

|
|

2) **Review the logs on NGINX Proxy cli for failure reasons**
   
  `sudo grep crit /var/log/nginx/error.log`

.. note :: What problem is identified in the nginx error logs?

|
|

3) **Fix the problem by increasing the rlimit**
This changes the limit on the number of open files that a worker process may have

In the NIM Console, edit nginx.conf file.

Increase rlimit to 4096, by uncommenting line 5

* worker_rlimit_nofile 4096; 

Publish the new configuration.

.. image:: /class8/images/nim-rlimit-4096.png  

|
|

4) **Run the same test again**
   
Review Locust graphs

.. note::  Were there improvements and were there still failures?
	
|

.. toctree::
   :maxdepth: 2
   :hidden:
   :glob: