Why Is the Migration Speed Slow Sometimes?

Updated on 2024-08-29 GMT+08:00

View PDF

The maximum migration speed of OMS is 500 Mbit/s. If you need a higher migration speed, you are advised to use storage migration workflows on MgC. MgC allows you to migrate data using dedicated, scalable migration clusters with up to 20 Gbit/s of bandwidth.

The migration speed is influenced by many factors, such as the sizes of the source objects, the number of objects being migrated, and the network transmission speed. If the migration network is normal, it may be that:

There are a large number of small objects.
A fixed maximum number of objects can be concurrently migrated in a migration task. Before migration, OMS lists the objects in the source bucket. After an object is migrated, OMS checks whether the object in the source bucket is consistent with that in the destination bucket. Compared with migration of large objects, for any given amount of data, it takes longer to list, compare, and migrate a larger number of smaller objects.

In this case, you can create a migration task group to intelligently split the source objects into multiple subtasks for concurrent migration. This can improve the migration speed.
There are a small number of large objects.
A separate thread is used to migrate each object. If there are just a few very large objects, for example, less than 50, the migration thread concurrency is low, which slows down the migration.

In this case, wait patiently.
NOTE:
- Large objects are uploaded in parts. Only the data volume of uploaded parts is counted as part of the migrated data volume. Therefore, the migration speed may fluctuate.
- The migration speed is recalculated every 5 seconds. If it takes more than 5 seconds to upload any individual part, the instantaneous speed is zero.
Archive data restoration is used when archive data is migrated.
A fixed maximum number of objects can be migrated concurrently in a migration task. If you do not restore the archive data in advance and rely on the archive data restoration function of OMS fully, the migration speed will be slow.

In this case, you can restore the archive data in batches on the source platform before the migration. For details, see Migrating Archive Data.
A large number of objects do not need to be migrated and are ignored during the migration.
During the migration, the system compares source objects with destination objects and determines which objects need to be migrated. If a large number of objects do not need to be migrated, they will be ignored, but identifying them still takes time, so the migration is slow.

In this case, wait patiently.

Parent topic: Migration Duration

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot