Jump to content

Lumi

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

About Lumi

Profile Information

  • OS
    Windows 7 x64

Lumi's Achievements

0

Reputation

  1. I installed the Hotfix Rollup and the three updates required as per the Hotfix Notice. http://support.microsoft.com/kb/2775511/en-us KB 2732673, 2728738, 2878378 Rebooted as required, then requested another boot log: xbootmgr -trace boot -resultPath C:\XBootMgr3 The result is here: interval name="PreSMSS" startTime="0" endTime="28453" duration="28453"> interval name="SMSSInit" startTime="28453" endTime="35494" duration="7041"> interval name="WinlogonInit" startTime="35494" endTime="41581" duration="6087"> interval name="ExplorerInit" startTime="41581" endTime="44898" duration="3317"> interval name="PostExplorerPeriod" startTime="44898" endTime="71498" duration="26600"> interval name="TraceTail" startTime="71498" endTime="176652" duration="105153"> PreSMSS increased by about seven seconds. The reason is the freshly hotfixed rdbss.sys, which now leads the ranking of sluggy drivers. No significant change for the RDP drivers. <pnpObject name="rdbss" type="Driver" activity="Load" startTime="19955" endTime="28408" duration="8452" prePendTime="8452"/> <pnpObject name="RDPREFMP" type="Driver" activity="Load" startTime="14698" endTime="19866" duration="5168" prePendTime="5168"/> <pnpObject name="\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\RDPREFMP" type="unknown" activity="unknown" startTime="14701" endTime="19866" duration="5165" prePendTime="5165"/> <pnpObject name="RDPCDD" type="Driver" activity="Load" startTime="4697" endTime="9698" duration="5000" prePendTime="5000"/> <pnpObject name="RDPENCDD" type="Driver" activity="Load" startTime="9698" endTime="14698" duration="5000" prePendTime="5000"/> <pnpObject name="\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\RDPCDD" type="unknown" activity="unknown" startTime="4700" endTime="9698" duration="4997" prePendTime="4997"/> <pnpObject name="\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\RDPENCDD" type="unknown" activity="unknown" startTime="9701" endTime="14698" duration="4997" prePendTime="4997"/> <pnpObject name="cdrom" type="Driver" activity="Load" startTime="4249" endTime="4682" duration="432" prePendTime="432"/> Guess the Hotfix Rollup was not needed, after all, and I'll have to take a look at the Procmon log. Other ideas? Update: Back to my original SysInternals Procmon forum post.
  2. First, this is a new boot log obtained by doing the bootPrep sequence (but without having installed the recommended hotfixes). <timing bootDoneViaExplorer="36204" bootDoneViaPostBoot="59004" osLoaderDuration="2988" postBootRequiredIdleTime="10000" postBootDisturbance="12800" pnpBootStartStartTime="110" pnpBootStartEndTime="1975" pnpBootStartDuration="1865" pnpSystemStartStartTime="4989" pnpSystemStartEndTime="21257" pnpSystemStartDuration="16268"> Second, the slow items are the same as in my Procmon log, the three RDP related drivers: <phase name="systemStart" startTime="4989" endTime="21257" duration="16268"> <pnpObject name="RDPENCDD" type="Driver" activity="Load" startTime="10655" endTime="15947" duration="5292" prePendTime="5292"/> <pnpObject name="\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\RDPENCDD" type="unknown" activity="unknown" startTime="10658" endTime="15947" duration="5289" prePendTime="5289"/> <pnpObject name="RDPCDD" type="Driver" activity="Load" startTime="5461" endTime="10654" duration="5194" prePendTime="5194"/> <pnpObject name="\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\RDPCDD" type="unknown" activity="unknown" startTime="5464" endTime="10654" duration="5191" prePendTime="5191"/> <pnpObject name="RDPREFMP" type="Driver" activity="Load" startTime="15947" endTime="21132" duration="5185" prePendTime="5185"/> <pnpObject name="\REGISTRY\MACHINE\SYSTEM\ControlSet001\services\RDPREFMP" type="unknown" activity="unknown" startTime="15951" endTime="21132" duration="5182" prePendTime="5182"/> <pnpObject name="cdrom" type="Driver" activity="Load" startTime="5017" endTime="5444" duration="427" prePendTime="427"/> Third, I'm attaching three screenshots. They show 370 MB of "Unknown" disk reads. I assume this is Prefetch? (Looks like only the first screenshot made it to the server. Will see if I can add the other two somehow.)
  3. [ origin: http://forum.sysinternals.com/topic30672.html ] Thank you, Andre. That's an interesting tutorial you've put together there … completely new to me! So I installed the Performance Tools (from the 8.1 distro) on the old platter disk, configured Windows Auto Logon, and issued the boot log command: xbootmgr -trace boot -resultPath C:\ I omitted the -traceFlags BASE+CSWITCH+DRIVERS+POWER because it would error out although I had already increased the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\ReadyBoot\MaxFileSize Parameter to 100 MB. 05.08.2014 17:30 3.641.720 boot_BASE+CSWITCH_1.cab 05.08.2014 17:30 93.323.264 boot_BASE+CSWITCH_1.etl 05.08.2014 17:36 143.793 boot_BASE+CSWITCH_1.summary.XML The timing node in the XML summary has the following attributes (values in milliseconds): bootDoneViaExplorer="37886"bootDoneViaPostBoot="59686"osLoaderDuration="2688" postBootRequiredIdleTime="10000"postBootDisturbance="11800" pnpBootStartStartTime="110"pnpBootStartEndTime="1991"pnpBootStartDuration="1882" pnpSystemStartStartTime="5039"pnpSystemStartEndTime="21405"pnpSystemStartDuration="16365"At just 60 seconds, this reads much better than what the eventvwr has to say, which is more than 100 seconds. Maybe that's because of the Auto logon? The following Quote from the site you linked to seems to confirm this assumption: »If auto-logon is not enabled, the time that elapses while the logon screen is displayed affects the measured boot time in a trace.« Interval data: interval name="PreSMSS" startTime="0" endTime="21416" duration="21416"> interval name="SMSSInit" startTime="21416" endTime="28522" duration="7106"> interval name="WinlogonInit" startTime="28522" endTime="33735" duration="5214"> interval name="ExplorerInit" startTime="33735" endTime="37886" duration="4151"> interval name="PostExplorerPeriod" startTime="37886" endTime="59686" duration="21800"> interval name="TraceTail" startTime="59686" endTime="165778" duration="106092"> Maybe this is not too bad after all for a laptop running a 2010 Intel dual-core i5-430 and a 1 TB 5400 U/min platter disk? I just read your tutorial page and the first two pages of comments, so I'm not aware of what might have been said in this huge thread … Anyway, guess I need to repeat that test on the SSD copy of my system. Have already run it once, but without auto logon, which I think (see above) skews the result.
×
×
  • Create New...