Add option to control Astaire CPU utilization.

Metaswitch · Apr 23, 2015 · b1ad30c · b1ad30c
1 parent 2bdcef4
commit b1ad30c
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/docs/Clearwater_Configuration_Options_Reference.md b/docs/Clearwater_Configuration_Options_Reference.md
@@ -90,6 +90,7 @@ This section describes optional configuration options, particularly for ensuring
 * `override_npdi` - Whether the I-CSCF, S-CSCF and BGCF should check for number portability data on requests that already have the 'npdi' indicator. This defaults to false
 * `exception_max_ttl` - determines the maximum time before a process exits if it crashes. This defaults to 600 seconds
 * `check_destination_host` - determines whether the node checks the Destination-Host on a Diameter request when deciding whether it should process the request. This defaults to true. 
+* `astaire_cpu_limit_percentage` - the maximum percentage of total CPU that Astaire is allowed to consume when resyncing memcached data (as part of a scale-up, scale-down, or following a memcached failure). Note that this only limits the CPU usage of the Astaire process, and does not affect memcached's CPU usage. Must be an integer. Defaults to 5.
 
 ## Experimental options