How Do I Disable Data Compression When the CPU Usage Is Too High During a Linux Block-Level Migration?

By default, data compression is enabled for Linux block-level migrations. The number of compression threads is configured based on the resource usage of the source server. The default value is the number of idle CPUs, and the maximum value is 3. Data compression may cause high CPU usage. In this case, you can disable this function in the SMS-Agent/agent/config/g-property.cfg file.

Go to the SMS-Agent installation directory and run the following command:

cd ./agent/config && vi g-property.cfg

Configure the following parameters.

• block.compress.thread.num: The number of compression threads. The value must be an integer ranging from 1 to 3. Generally, the value is automatically set by the Agent based on the source server conditions. You can change it manually.
• block.node.cache.size.MB: The size of a single data cache node. There are six cache nodes configured on the source server by the Agent. The value must be an integer ranging from 1 to 8. The default value is 4.
• block.need.compress: controls whether to compress data during transmission. The value can be True or False. If you do not want to compress data during transmission, set this parameter to False.

Data compression occupies a large amount of CPU resources. When you configure this function, you need to consider the actual resource usage of the source server to prevent services on it from being affected. For details about the default resource usage, see Resource Usage Description for Linux Block-Level Migrations.