[checkmk-commits] 6702 Introduced various performance improvements for cmc config generation (e.g. multiprocessing)

Module: check_mk Branch: master Commit: 970cbe7a825cbc4724b262c36af2bef5cb3f5065 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=970cbe7a825cbc… Author: Andreas Boesl &lt;ab(a)mathias-kettner.de&gt; Date: Fri Jan 25 13:29:34 2019 +0100 6702 Introduced various performance improvements for cmc config generation (e.g. multiprocessing) Previous versions only used one CPU core for the config generation. The time to generate the config highly depends on the number of hosts, services and especially rulesets. Lots of the underlying computation code has been changed, caches and functions were optimized. As a result Check_MK is now able to distribute the work load of the config generation over several CPUs. Per default, this feature is activated. Unless configured otherwise, it uses up to 75% of the available CPUs during the configuration generation, leaving some CPUs for running monitoring core. A new configuration option <tt>Generate monitoring configuration via multiprocessing</tt> has been introduced. You can either switch of multiprocessing or configure the number of used CPUs manually. Change-Id: I0d3da33f45fa41cc963aca013f815b23d87bd8f5 --- .werks/6702 | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/.werks/6702 b/.werks/6702 new file mode 100644 index 0000000..55527dc --- /dev/null +++ b/.werks/6702 @@ -0,0 +1,21 @@ +Title: Introduced various performance improvements for cmc config generation (e.g. multiprocessing) +Level: 2 +Component: cmc +Compatible: compat +Edition: cee +Version: 1.6.0i1 +Date: 1548418345 +Class: feature + +Previous versions only used one CPU core for the config generation. +The time to generate the config highly depends on the number of hosts, services and especially rulesets. + +Lots of the underlying computation code has been changed, caches and functions were optimized. +As a result Check_MK is now able to distribute the work load of the config generation over several CPUs. + +Per default, this feature is activated. Unless configured otherwise, it uses up to 75% of the available +CPUs during the config generation, leaving some CPUs for running monitoring core. +A new configuration option <tt>Generate monitoring configuration via multiprocessing</tt> has been introduced. +You can either switch of multiprocessing or configure the number of used CPUs manually. + +Tests have shown that the performance can increased by a factor of 5-10 on a 8 CPU core setup.