Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Tuning the System

A number of Control Center parameters can be tuned according to the available resources and the system load. These include:

  • /etc/netrounds/netrounds.conf
    • CALL_EXECUTER_MAX_CHILDREN: This configures how many background jobs can run in parallel. The default is 20. Each test and monitor (not each task) will periodically run as a background job. If you have many tests or monitors, you might want to set this value to match the number of running tests and monitors to prevent those jobs from queuing up and delaying the collecting of data. The current queue length can be seen as the scheduled_call_latency parameter returned by the ncc status command.
  • /etc/apache2/sites-available/netrounds-ssl.conf
    • WSGIDaemonProcess netrounds ... processes: This configures how many HTTP requests to the Control Center GUI can be handled at the same time. The default is 10. If you have many or slow requests, you might need to increase this number. If no worker is available to start processing a request, a 504 Gateway Timeout response will be returned.
  • /etc/postgresql/9.5/main/postgresql.conf

REST API rate throttling can be applied in the file

  • /etc/netrounds/restol.conf

    • The settings RATE_LIMIT_ENABLED and RATE_LIMIT_DEFAULT are used for throttling REST API requests. To enable throttling, set RATE_LIMIT_ENABLED=True.
    • Then configure the RATE_LIMIT_DEFAULT setting to indicate the maximum frequency of API requests from the same IP address. For example, RATE_LIMIT_DEFAULT=30/second will allow up to 30 requests per second from each IP address. The rate limit can be set per second, minute, hour, or day. It is also possible to set multiple limits, as in RATE_LIMIT_DEFAULT=30/second,60/minute.
    • To disable throttling, set RATE_LIMIT_ENABLED=False.