- Local time
- 3:14 PM
- Messages
- 37
...and can/should I uninstall the SDK, btw?
My Computer
- Computer Manufacturer/Model Number
- Lenovo thinkpad W520
- OS
- Windows 7 Pro SP1 64 bit
- CPU
- i7-2720
- Memory
- 8GB 1600GHz
- Hard Drives
- 80gb mini ssd
300gb hdd
.First of all, I'm wondering why the opening of the cntl panel calls up MessageCenter Plus. Is there an obvious logic to that and might it be avoided? It would explain the unchanged part of the delay.cmdagent.exe is causing an inordinate amount of file I/O (specifically QueryInfo calls) and WMI calls during the time that the shell (explorer.exe) is querying the registry for CLSIDs to display information (and what MUI / language to use, etc) to display control panel items. This is approximately 5-6 seconds of delay - this is also exacerbated near the end with opera.exe's file I/O (at close to 100% of the total disk I/O time during this timeframe).
Lenovo's MessageCenter Plus takes 7.9 seconds to initialize once the control panel itself starts to load, which delays the load of the control panel. The control panel finishes loading once MCP loads in 0.3 seconds.
), uninstall. They're not helping anything, at the very least.Thank you!Post away.
xperf -on DIAG+DISK_IO_INIT+DRIVERS+FILE_IO+FILE_IO_INIT+FILENAME+NETWORKTRACE+PRIORITY+PROFILE+REGISTRY+SPLIT_IO
Hmm that's a years old file from when I had an old PowerBook G4Interesting - all of your read time appears to go to a file called "I:\CESAR\STUFF\.DS_Store\Other\capture-2.avi" while opening any of the applications, which is the bulk of the ~70 seconds of time for opening Firefox, ~77
The applications themselves do not take up more than a few seconds of each of those time periods, so something running within the LocalSystemNetworkRestricted svchost is chewing up disk time (at almost 100%, but doing low-priority reads). Looking closer at the threads doing the read, it's coming from the sysmain.dll thread inside that svchost, which is SuperFetch/ReadyBoost. If you don't have a ReadyBoost key in that machine, try disabling the SuperFetch service for the time being to see if that changes the behavior at all.
I didn't think it would, but anything was possible. The other option I didn't specify was to delete the file and run a defrag against all your volumes (with defrag /u /v from an elevated cmd prompt) to update the superfetch information.