| Reporter |
Brian (oliwa)
|
|---|---|
| Created | Jan 14, 2012 8:59:16 PM |
| Updated | Jan 14, 2012 8:59:16 PM |
| Priority | Show-stopper |
| Type | Performance Problem |
| Fix versions | No Fix versions |
| State | Open |
| Assignee | Sergey Coox (coox) |
| Subsystem | No subsystem |
| Affected versions | 6.1 |
| Fixed in build | No Fixed in build |
I have PerfWatson from Microsoft installed along with PerfWatson monitor so I can monitor the performance of the UI thread. I have a simple solution with 1 test project and 1 test that when I try to run the test the UI thread in VS spikes above 2 seconds approximately 10 times in a row. This is the easiest way I have found to reproduce this.
Most of the time I will be coding and all of a sudden VS is unusable for about 20 to 30 seconds while the UI thread exceeds a 2 second wait time. The rest of time the UI thread stays responsive and I don't have any issues. I set a stop watch and it happens about every 5 minutes.
My uploaded trace file is called HappySteveYzermanDay.rar
If I disable Resharper I don't see any issues. The UI thread spikes 1 times during the compilation and that's it.
If I disable PerfWatson I don't see the same slowdown but it's hard to know for sure without being able to visually see the UI thread response.
I don't see where I can set the severity but after 3 months I finally can reproduce it and can trace it. This has caused a lot of frustration and is getting to the point that it is a major hindrance.
Most of the time I will be coding and all of a sudden VS is unusable for about 20 to 30 seconds while the UI thread exceeds a 2 second wait time. The rest of time the UI thread stays responsive and I don't have any issues. I set a stop watch and it happens about every 5 minutes.
My uploaded trace file is called HappySteveYzermanDay.rar
If I disable Resharper I don't see any issues. The UI thread spikes 1 times during the compilation and that's it.
If I disable PerfWatson I don't see the same slowdown but it's hard to know for sure without being able to visually see the UI thread response.
I don't see where I can set the severity but after 3 months I finally can reproduce it and can trace it. This has caused a lot of frustration and is getting to the point that it is a major hindrance.