1
votes

I'm very frustrated by the slowness of the OpsHub migration utility. I've even moved our TFS infrastructure to Azure just so that I could pump things through faster, but the gains are minor.

One of the things I noticed was that the TFS_Temp folder (C:\Program Files\OpsHub Visual Studio Online Migration Utility\TFS_Temp) is being hit with a bit of random IO.

So, my question is how can I tell OpsHub to use a different drive location (where Random IO is better processed) for the TFS_Temp folder?

2

2 Answers

1
votes

OK I'm using a workaround using Symbolic Links.

First I move the actual TFS_Temp folder, and then symlink that new location back to the original path:

mklink /J "C:\Program Files\OpsHub Visual Studio Online Migration Utility\TFS_Temp" D:\TFS_Temp

1
votes

The TFS_Temp is the folder which the utility maps to an additional drive for the system (usually O:\ by default, and additional ones if the path is too long for some files). This is where the utility creates a workspace of your VSO.

And the migration utility utilizes this space for data processing of each changeset. Hence a lot of IO processing. However, this location is hard coded and non-modifiable directly through any configuration.

But glad to know you got is working through symbolic links. Has it improved your performance?