VS2010: Using profiler to improve cache data locality

A recent Concurrency Hazards: False Sharing article demonstrates how VS2010 profiler can be used to detect source of cache data locality issues. To achieve this, you can sample with cache specific CPU performance counters, as long as you do not run inside Virtual Machine or on Hyper-V enabled environment (and this is why). In post-VS2010…

0

PRF0025: No data was collected – why is that?

One day, you may try to use Visual Studio profiler to sample an application you develop, and end up with an error saying no data is collected: Profiling started.Profiling process ID 2752 (<Your Application Name>).Process ID 2752 has exited.Data written to C:\<some path>\Report100114.vsp.Profiling finished.PRF0025: No data was collected. Profiling complete. There could be number of…

0

VS 2008 Profiler and Nehalem Intel Processor

When you run VS 2008 SP1 profiler on Intel Nehalem CPU based machine, you may experience crash of operating system (blue screen). This problem occurs because the sampling profiler uses a kernel mode driver in the operating system. However, the Intel Nehalem processor was created after the release of the 2008 version of the profiler,…

0

Visual Studio Profiler in Virtual Environment

Visual Studio profiler usage on virtual machines was limited so far, as it didn’t support Sampling mode in such environment. I’m glad to note that in Visual Studio 2010 you can sample your applications inside of virtual machines. VMs could be created using either VPC, VMWare of Hyper-V technologies. Some hardware is not virtualized, though,…

0