3 ms·

Unfortunately I can't really provide advice for your local workspace troubles as I work on the Git side of things. I'm sorry to hear about your performance tro

Unfortunately I can't really provide advice for your local workspace troubles as I work on the Git side of things. I'm sorry to hear about your performance troubles with local workspaces: 100,000 files in a local workspace should not be at the upper limits, I wouldn't think. Many people 'round these parts were using local workspaces for their VS 2013 development: my working folder mappings appear to be 25 GB and 120,000 files for VS 2013. Concurrency and locking, of course, could affect that, but I'm still surprised. I trust you're not doing anything wacky like trying to put your working folders on USB sticks or SMB mounts, so I would recommend either opening a question on the MSDN support forum or (better) opening a support ticket. Our support engineers are really quite good and might be able to assist, or at least understand why you're seeing this performance with local workspaces. (I regret that we cannot fix your internet provider.)

louthy 12y ago
Heh, thanks for the response :) I realise you can't do anything for me, I just thought I'd give you a sense of the frustration of the local-workspace route. The fact it's slower and less reliable than the server-workspace approach is pretty crazy. > I trust you're not doing anything wacky like trying to put your working folders on USB sticks or SMB mounts Nothing crazy, repository is sitting on an SSD drive. If you're working on the Git side, then all I can say is: great job! I'm hoping to move our source repository over Git soon... I can't handle staying with server/local workspaces much longer, but as with all things like this it's about finding the right moment for the team to switch.