[checkmk-commits] [tribe29/checkmk] aa8aeb: 10535 Activate Changes: Now able to reduce the num...

Branch: refs/heads/1.6.0 Home: https://github.com/tribe29/checkmk Commit: aa8aebb63973e2182603ec4e397190a299304221 https://github.com/tribe29/checkmk/commit/aa8aebb63973e2182603ec4e397190a29… Author: Andreas Boesl &lt;andreas.boesl(a)tribe29.com&gt; Date: 2020-05-04 (Mon, 04 May 2020) Changed paths: A .werks/10535 M cmk/gui/plugins/config/base.py M cmk/gui/plugins/wato/check_mk_configuration.py M cmk/gui/plugins/wato/utils/__init__.py M cmk/gui/watolib/activate_changes.py A cmk/gui/watolib/wato_background_job.py M tests/unit/cmk/gui/test_background_job.py M tests/unit/cmk/gui/watolib/test_watolib.py M web/htdocs/js/modules/activation.js Log Message: ----------- 10535 Activate Changes: Now able to reduce the number of maximum working apache processes You can now configure how much apache processes are spawned during the activate changes phase. In previous versions each site with a change always had one dedicated apache process. All of these processes were spawned at the same time. This consumed quite an amount of memory when your WATO setup included lots (>50) of sites. This werk introduces a scheduler mechanism, which ensures that <ul> <li>all sites with changes are updated</li> <li>the number of apache processes do not go through the roof</li> </ul> Per default the optimal number is automatically calculated (up to 90% of RAM is used), which should be OK for most setups. The new global settings option <tt>Maximum parallel processes during activate changes</tt> allows you to adjust this value. The hardcoded minium value is 5. Change-Id: I33dfb5d5c6932fd8f45fc2df9185ad091a0403d5