magento / magento/data-migration-tool

Use multiple cores?

Open
#650 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request up for grabs
Dominant language
PHP
Stars
339
Forks
195
PR merge metrics
No merged PRs in 30d

Description

The data migration tool does not appear to make use of all cores - is this possible?

I have spun up a 32 core instance, which I hoped would make this process quicker.

At the moment I am looking at a 3 hour conversion time for a Magento 1 30GB SQL database on my local machine, which is a Dell 9560 (4 core i7).

### Preconditions
1. Magento 1.14.4.0
2. Magento 2.3.0
3. PHP 7.2.14
4. MySQL 5.7.25

### Steps to reproduce
1. bin/magento migrate:data ..

### Expected result
1. All cores to be used

### Actual result
1. Only 1 core used
2. See screenshot
![screenshot from 2019-02-07 15-50-21](https://user-images.githubusercontent.com/1188869/52423472-1b4c1780-2af0-11e9-9fb3-a9921beb1fbc.png)

Also, what affect does bulk_size have?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing bin/magento migrate:data with the listed Magento, PHP, and MySQL versions and compare CPU usage during the 30GB migration. Investigate how the migration process uses cores and what bulk_size affects; done means a documented or implemented answer to both questions, with measured results.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql, php
Domain
databases, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.