openstack/vitrage
Code Issues Proposed changes
Files
227e8f69df5747989ba3a3aada1b9787ec00bda7
vitrage/doc/source/contributor/high-scale.rst
Idan Hefetz 842f9d6cea Complete removal of vitrage-collector service. 
- vitrage-graph will execute the drivers.
 - Simplify large data transfer from drivers to processor by obsoleting rpc.
 - Drivers don't need to create the complete list by taking advantage of python
   generators in order to conserve memory.
 - Lowering the total signiture of vitrage processes.
 - LockByDriver will enforce a driver does not run get_changes and get_all in parallel.

Story: 2004384
Change-Id: Ie713456b2df96e24d0b15d2362a666162bfb4300
2018-11-21 08:15:12 +00:00

3.9 KiB
Raw Blame History

Configure Vitrage for high-scale

In a production environment with > 50,000 entities, the following configuration changes are suggested:

Tune RPC

Vitrage-api uses RPC to request data from vitrage-graph, these requests take longer, and there may be a need to increase the timeout. The following should be set in /etc/vitrage/vitrage.conf, under [DEFAULT] section:

Name Description Default Value Suggested Value
rpc_response_timeout Seconds to wait for a response from a call

60

300

To apply, restart these:

sudo service vitrage-graph restart

Restart the Vitrage api (either vitrage-api or apache)

Tune Memory

Most of the data is held in-memory. To conserve memory usage, the number of evaluator workers should be decreased. If using many Vitrage templates the number of evaluator workers can be increased, but kept to a minimum needed.

The following should be set in /etc/vitrage/vitrage.conf, under [evaluator] section:

Name Description Default Value Suggested Value
workers Number of workers for template evaluator number of cores

1

The default api workers count is 1. Increasing it will reduce the latency of parallel api calls, but will result in higher memory consumption. If the graph contains large amounts of entities, reducing this will reduce the memory consumption dramatically.

The following should be set in /etc/vitrage/vitrage.conf, under [api] section:

Name Description Default Value Suggested Value
workers Number of workers for api handler 1

1

To apply, run sudo service vitrage-graph restart

Tune Mysql

Vitrage periodically persists the graph to mysql, as a mysql blob. As the graph size increases, it is recommended to increase the mysql max_allowed_packet.

The following should be set in /etc/mysql/my.cnf, under [mysqld] section:

Name Description Default Value Suggested Value
max_allowed_packet

The maximum size of one packet or any string

 4M-64M

100M

To apply, run sudo service mysql restart