Visual Studio 2010 Stand Alone profiler not collecting data in sampling mode

已鎖定 Visual Studio 2010 Stand Alone profiler not collecting data in sampling mode

  • Monday, August 15, 2011 5:39 PM
     
     

    Hi,

    I am trying to collect performance data using the Visual Studio 2010 Stand alone Profiler in sampling mode on a Win2K8 server m/c.

    The process that I am trying to profile is a 32 bit process and I am using the version of the Profiler as specified in the documentation.

    The attach is successful and I have collected the data for over 1 hour. When I try to open the .vsp file in Visual Studio 2010 in my development m/c I get the following message "File contains no data buffers".

    I tried creating a report on the profiled m/c and I get the same message.

    What could be wrong? Thanks in advance for your help.

    Here are the commands that I am issuing and the responses:-

    C:\vs_2010_profiling>vsperfclrenv /sampleon
    Enabling VSPerf Sampling Attach Profiling. Allows to 'attaching' to managed applications.

    Current Profiling Environment variables are:
    COR_ENABLE_PROFILING=1
    COR_PROFILER={F1216318-0905-4fe8-B2E8-105CEB7CD689}
    COR_LINE_PROFILING=1
    COR_INTERACTION_PROFILING=0
    COR_GC_PROFILING=0
    CORECLR_ENABLE_PROFILING=1
    CORECLR_PROFILER={F1216318-0905-4fe8-B2E8-105CEB7CD689}

    C:\vs_2010_profiling>vsperfcmd /start:sample /output:test2.vsp /CS
    Microsoft (R) VSPerf Command Version 10.0.30319 x86
    Copyright (C) Microsoft Corp. All rights reserved.



    C:\vs_2010_profiling>vsperfcmd /attach:test.exe
    Microsoft (R) VSPerf Command Version 10.0.30319 x86
    Copyright (C) Microsoft Corp. All rights reserved.


    Successfully attached to process ID:472

    C:\vs_2010_profiling>vsperfcmd /detach
    Microsoft (R) VSPerf Command Version 10.0.30319 x86
    Copyright (C) Microsoft Corp. All rights reserved.


    Successfully detached from all processes

    C:\vs_2010_profiling>vsperfcmd /shutdown
    Microsoft (R) VSPerf Command Version 10.0.30319 x86
    Copyright (C) Microsoft Corp. All rights reserved.


    Shutting down the Profile Monitor
    ------------------------------------------------------------

    C:\vs_2010_profiling>VSPerfReport test2.vsp /output:. /summary:all

    Microsoft (R) VSPerf Report Generator, Version 10.0.0.0
    Copyright (C) Microsoft Corporation. All rights reserved.

    File opened
    Successfully opened the file.
    A report file, test2_Header.csv, has been generated.
    A report file, test2_MarksSummary.csv, has been generated.
    File contains no data buffers
    File contains no data buffers
    Analysis completed
    A report file, test2_RuleWarningsSummary.csv, has been generated.


    KSubramanian

All Replies

  • Monday, August 15, 2011 7:42 PM
     
     

    What kind of process is your application ? IS it a service as your not starting it and your trying to do CrossSession ampling and attatching to it ?

    If its a service, try follwoing the following How to: Attach the Profiler to a .NET Service to Collect Application Statistics by Using the Command Line http://msdn.microsoft.com/en-us/library/dd255409.aspx

    Basicly it adds /GlobalSampelsOn and a restart, before you start profiling, and uses either /GlobalOn or /ProcessOn  to start collectiong data.

     

  • Monday, August 15, 2011 8:34 PM
     
     

    Thanks for the reply.

    It is not a service. I started the application standalone and then tried attaching to it. I will try your suggestion of launching it with the profiler.


    KSubramanian
  • Monday, August 15, 2011 9:50 PM
     
     

    You could try this Walkthrough: Command-Line Profiling Using Sampling http://msdn.microsoft.com/en-us/library/aa985628.aspx

    Some other hints, Are you sure your using the right 32/64 bits profiler tools for your application, is your application compiled for x86 or Any CPU ?

    Verify its not related to UAC issues

  • Wednesday, August 17, 2011 3:16 PM
     
     Answered

    Thanks for your suggestions. I finally managed to get sampling profile data. My issue was I was running the profiling tools from a 32 bit console. When I switched to a 64 bit console the data was collected.

     


    KSubramanian