Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Server Migration Service/ FAQs/ Target Server Configuration/ How Do I Limit Resource Allocation for the Agent in a Linux Migration?

How Do I Limit Resource Allocation for the Agent in a Linux Migration?

Updated on 2025-01-24 GMT+08:00

You can limit how many CPU, memory, and disk throughput resources of the Linux source server can be used by the SMS-Agent.

Precautions

Limiting resources for SMS-Agent requires the built-in cgroups feature on Linux. If cgroups on the source server is broken or abnormal, the resource limits may not be applied. If you need help, contact SMS technical support.

Prerequisites

Cgroups has been installed and enabled on the source server.

To check if it has been installed, run the following command on the source server:

mount | grep cgroup

If the cgroups (V1 or V2) mounting information is displayed, cgroups is enabled on the source server. Otherwise, it is not.

Before setting resource limits on the SMS console, evaluate whether installing or enabling cgroups will affect services on the source server. If source services use cgroups, submit a service ticket to ask SMS migration experts whether the SMS resource limits conflict with the source services.

  • Cgroups V1

    The example output shows that the following three mount points were attached to the CPU, memory, and disk I/O controllers, respectively.

    • /sys/fs/cgroup/CPU,CPUacct
    • /sys/fs/cgroup/memory
    • /sys/fs/cgroup/blkio
  • Cgroups V2

    Cgroups V2 is mounted on /sys/fs/cgroup. Unlike V1, cgroups V2 has no mount points attached to specific resources.

Procedure

  1. Sign in to the SMS console.
  2. In the navigation pane on the left, choose Servers.
  3. In the server list, locate the source server to be migrated and click Configure Target in the Migration Stage/Status column.
  4. Expand Resource Limits (Optional), read parameter description and precautions carefully, and set CPU Limit, Memory Limit, and Disk Throughput Limit.

    Table 1 Parameters for setting resource limits

    Parameter

    Description

    Precaution

    CPU Limit

    Controls the maximum percentage of CPUs to be used by the SMS-Agent on the source server.

    • If this parameter is left blank, the CPU usage of SMS-Agent is not limited.
    • 1% ≤ CPU limit (integer) ≤ 100%
    • To ensure a smooth migration, allocate at least 0.2 CPUs to SMS-Agent.

    Formula: CPU limit (%) = Maximum number of CPUs allowed for SMS-Agent/Total number of CPUs × 100%

    For example:

    If the source server has 4 CPUs, and you want to allocate 0.5 CPUs for SMS-Agent, you can enter 13% (0.5/4 × 100%).

    • The CPU limit and disk throughput limit may affect the migration speed.
    • When the resource limits are applied, a folder named sms_mig_cgroup will be created in /sys/fs/cgroup on the source server, and parameters for configured limits are created here.

    Memory Limit

    Controls the maximum of memory to be used by SMS-Agent. If the configured limit is reached, SMS-Agent will be stopped or ended.

    • If this parameter is left blank, the memory usage of SMS-Agent is not limited.
    • 200 MB ≤ Memory Limit ≤ 1,000 MB
    • To ensure a successful migration, allocate at least 200 MB of memory to SMS-Agent.

    Disk Throughput Limit

    Controls the maximum disk throughput to be used by SMS-Agent. After the limit is set, the disk read/write speed of SMS-Agent will not exceed the limit.

    • If this parameter is left blank, the disk throughput of SMS-Agent is not limited.
    • 10 MB/s ≤ Disk Throughput Limit ≤1,000 MB/s
    • To ensure a successful migration, allocate at least 10 MB/s.

Modifying Resource Limits

You can modify resource limits if a task has a target server configured but is not started, is paused, or is waiting to execute an incremental synchronization. After locating the task, in the Operation column, choose More > Manage Migration Settings > Set Migration Limits. Then you can modify the resource limits.

Viewing Resource Usage

You can run the top or iotop command on the source server to view the resource usage during the migration. It is normal for the resource usage of SMS-Agent to slightly exceed the configured limits.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback