We have a 50GB on-premises TFS collection, which we want to have migrated to TFS online. We are now using the OpsHub Visual Studio Online Migration Utility, to test with. The conversion of some separate test projects seem to work fine, so now we are trying to measure the time it will take for a full migration. It looks like the migration of all 78K changesets will take about a month. That is way too long for us. The tool is using only one Core of our 8 available Cores. I don't see other resource bottlenecks, other than the CPU (the Core in use is over 50% most of the time). Are there any tips for a faster migration? Is there any way to speed up things? Besides asking you all for a possible solution, I am now also trying to do several smaller migrations in parallel. As soon as I have results of that, I will share them.
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效,请关闭广告屏蔽插件后再试):
问题:
回答1:
Which version you are using? There is performance issue with label which is fixed in version 1.0.1.005.
If your projects are independent in commit (Branch and Merge operation) then you can create migration, project wise which run parallel.