locked
Performance Monitor: Start at boot RRS feed

  • Question

  • Hi,

    Can anybody tell me how to get Performace Monitor to start Data Collecting automatically after reboot. I can't seem to find any option for that. Only Schedule and that's not really helpfull in my case. I would like to Collect Data about 10 min. after the login (and during login if possible).

    I am trying to identify why the start process is so slow when users logs in (Vista\Win7). I can see that there is a lot of IO -activity and I need to identify what process is causing that.

    Thanks

    /lakend

    Friday, September 3, 2010 6:49 AM

Answers

  • You should make a boot trace:

    http://www.msfn.org/board/index.php?showtopic=140247

    add the -postBootDelay [seconds] command line parameter to capture increase the time when the data are captured.

    When you open the etl file you can see the IO activity graph, select the internal, make a right click and select summary table. Now you can see whci hprocess causes the IO activity.

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Arthur Xie Thursday, September 9, 2010 8:00 AM
    Friday, September 3, 2010 10:54 AM
  • lakend,

    If you want to troubleshoot boot performance issues.
    I recommend that you use Xpref from the windows performance toolkit.
    http://msdn.microsoft.com/en-us/performance/cc825801.aspx

    You can configure Xpref to run at boot time and it will give more information that the performance monitor ever give you.
    Here is a link to the quick start guide.
    http://msdn.microsoft.com/library/ff190975

    And here is a pratical tutorial.
    http://blogs.microsoft.co.il/blogs/sasha/archive/2008/03/15/xperf-windows-performance-toolkit.aspx

    Kind Regards
    DFT


    IM me - TWiTTer: @DFTER
    • Marked as answer by Arthur Xie Thursday, September 9, 2010 8:00 AM
    Friday, September 3, 2010 11:02 AM
  • Another useful information is the following log in Event Viewer.

    Application and service logs/Microsoft/Windows/Diagnostics-Performance/Operational

    The logs with IDs 100 and 101 records the boot processes and the time consuming of each process.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Thursday, September 9, 2010 8:00 AM
    Tuesday, September 7, 2010 7:46 AM

All replies

  • You should make a boot trace:

    http://www.msfn.org/board/index.php?showtopic=140247

    add the -postBootDelay [seconds] command line parameter to capture increase the time when the data are captured.

    When you open the etl file you can see the IO activity graph, select the internal, make a right click and select summary table. Now you can see whci hprocess causes the IO activity.

    André


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Arthur Xie Thursday, September 9, 2010 8:00 AM
    Friday, September 3, 2010 10:54 AM
  • lakend,

    If you want to troubleshoot boot performance issues.
    I recommend that you use Xpref from the windows performance toolkit.
    http://msdn.microsoft.com/en-us/performance/cc825801.aspx

    You can configure Xpref to run at boot time and it will give more information that the performance monitor ever give you.
    Here is a link to the quick start guide.
    http://msdn.microsoft.com/library/ff190975

    And here is a pratical tutorial.
    http://blogs.microsoft.co.il/blogs/sasha/archive/2008/03/15/xperf-windows-performance-toolkit.aspx

    Kind Regards
    DFT


    IM me - TWiTTer: @DFTER
    • Marked as answer by Arthur Xie Thursday, September 9, 2010 8:00 AM
    Friday, September 3, 2010 11:02 AM
  • Another useful information is the following log in Event Viewer.

    Application and service logs/Microsoft/Windows/Diagnostics-Performance/Operational

    The logs with IDs 100 and 101 records the boot processes and the time consuming of each process.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Thursday, September 9, 2010 8:00 AM
    Tuesday, September 7, 2010 7:46 AM
  • Application and service logs/Microsoft/Windows/Diagnostics-Performance/Operational

    This is just a summary. To get the full data you must follow my guide and make a compete boot trace.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, September 7, 2010 12:03 PM