What version of the software are you running?
This is on VX2.1 Update 8
Our engineering teams have looked into this question and done some comparative tests with VX.2.3 on a related but different issue. In VX.2.1 and VX.2.2 we did see perfromance differences compared to VX.2.3. We believe these differences and general improvement in VX.2.3 are related to a change we discovered in a Microsoft library we were using in the VX.2.1/2.2 releases. We cannot however confirm the tests we carried out relate directly to the issue you are seeing. For that we would need a test case an information regarding your configuration.
We are seeing this collectively across our organization. so it seems to not be a localized issue for us. Thanks for your reply and insight on 2.3