From OCS Inventory NG
Jump to: navigation, search

Management server tuning.

OCS Inventory NG management server needs some tuning to support the load of a large number of inventoried computers. Performances are just limited by the hardware configuration (especially the amount of RAM, processor is not very loaded) of computer hosting the 3 main components:

  • MySQL Datenbankserver.
  • Kommunikationserver.
  • Administrationsserver.
  • Verteilserver.

Zum Beispiel, our production server manages more than 70 000 clients. For this, we have 3 servers running Linux Debian Sarge, one for the Datenbankserver und the Kommunikationserver, another one for Administrationskonsole and a replica of Datenbankserver (we choose to replicate database on Administration server to avoid Administrationskonsole SQL queries using CPU and MySQL connextions of database used by Kommunikationserver) and the last one for deployement server. Hardware configuration for servers is the following:

  • 1 Intel Pentium Xeon 2,8 GHz.
  • 3 GB RAM

Because of the amount of available RAM, we have to limit the number of simultaneous HTTP-Verbindungen to Communication and Administration server to 400.

You must keep an eye on Apache web server logs for Kommunikationserver to detect any problems. Also, check Kommunikationserver log file in directory “/var/log/ocsinventory-NG”.

If you want to upgrade the number of simultaneous connections, you must update the “MaxClients” directive in Apache configuration file, usually “/etc/httpd/conf/httpd.conf”.

Refer to Apache tuning guidelines on Apavhe web site ( for more information.

Also, MySQL Datenbankserver is limited by default to 100 simultaneous connections. So, if the Kommunikationserver handles more than 100 simultaneous requests for inventory, it will not be able to answer all. You can upgrade this value by updating the “max_connections” MySQL variable for mysqld daemon.

Here is sample recommdations found on MySQL web site, using server with different amount of physical memory.

Parameter 800 MB 1.7 GB 2.4 GB
Table_cache 64M 64M 64M
Key_buffer 128M 256M 256M
Sort_buffer_size 2M 2M 2M
Read_buffer_size 2M 2M 2M
Read_rnd_buffer_size 4M 4M 4M
Myisam_sort_buffer_size 64M 64M 64M
Query_cache_size 128M 128M 128M
InnoDB_buffer_pool_size 384M 1024M 1700M
InnoDB_additional_mem_pool_size 20M 20M 20M
InnoDB_log_buffer_size 8M 8M 8M

Refer to MySQL tuning guidelines on MySQL web site ( für weitere Informationen.