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.
相关问题
- Getting error: File extension specified '.webt
- Using TFS command line tf.exe how can I copy a rep
- TFS Power tools Migrate doesn't actually migra
- What is the difference between tfpt scorch and tfp
- TFS 2017 Agent: and error occured while sending th
相关文章
- Is it possible to do a “destroy history” in TFS?
- How do I make a TeamCity build appear in the TFS B
- TFS vs. JIRA/Bamboo/SVN [closed]
- Why doesn't my .tfignore file ignore my packag
- Is it possible to create a docker container from T
- How to Move TFS 2010 Build Definition between Proj
- How to fix TF246017 The Team foundation server cou
- How to open TFS Power Tools - Alerts Explorer
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.