使用OpsHub工具从本地到在线TFS的TFS缓慢迁移 [英] Slow TFS migration from on-premise to TFS online with OpsHub tool

问题描述

我们有一个50GB的本地TFS集合，我们希望将其在线迁移到TFS.我们现在使用OpsHub Visual Studio在线迁移实用程序进行测试.某些单独的测试项目的转换似乎可以正常工作，因此现在我们尝试衡量一次完整迁移所需的时间.似乎所有78,000个变更集的迁移都将花费大约一个月的时间.对我们来说那太长了.该工具仅使用我们8个可用内核中的一个.除了CPU以外，我看不到其他资源瓶颈(大多数情况下，使用的Core超过50％). 有什么技巧可以加快迁移速度吗?有什么办法可以加快速度吗? 除了要求大家提供可能的解决方案之外，我现在还尝试并行进行几个较小的迁移.取得结果后，我将分享它们.

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.0.1.005版中修复.

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.

这篇关于使用OpsHub工具从本地到在线TFS的TFS缓慢迁移的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！