CoreTemp 1.0 RC4 is slow

[SClemente]

Since installing CoreTemp v1.0 RC4, it now takes 30+ seconds to load after everything else has loaded. I am running Win7 64-bit Pro with a solid state cache drive to speed up things. Intel Core i7-2600 (3.4 GHz), 16GB RAM. My PC boots fast, but is now held up by CoreTemp. Any ideas on why? The website says v1.0 RC4 should load 2 to 4x faster.

[The Coolest]

This is strange indeed. What happens if you start Core Temp after the system has already started?
Does it still take a long time to start or does it start quickly?
And in 1.0 I reorganized much of the code to make Core Temp start much faster, in my tests I saw improvements up to x10 in startup speed on really slow machines and it is about x2-x4 faster on modern systems than the old 0.99.x versions.

[SClemente]

Thank you for the quick reply. I did a reboot (twice) without Core Temp loading at startup. Using this method, when I start Core Temp manually it loads virtually instantaneously (<1 sec). Nice job. Thank you. (That was meant as a compliment, not sarcasm).

Here is some more background that may or may not have any relevance. I am running the following gadgets: 1) All CPU Meter v4.5 by Addgadgets (requires Core Temp); 2) Core Temp Gadget v2.7 by you; 3) Network Meter v8.5 by Addgadgets; 4) Drives Meter v4.1 by Addgadgets, and; 5) GPU Meter v2.3 by Addgadgets. All are the latest versions. Only items 1) and 2) requires Core Temp to be running.

During Windows startup, all the gadgets load very quickly. The previous versions of Core Temp (i.e. <v1.0) all loaded quickly with these same gadgets. Once I installed v1.0 RC4, Core Temp load time slowed down markedly. I tried uninstalling and reinstalling a version earlier than v1.0, but apparently some of the registry settings remain, so v1.0 ended up being installed again.

Any suggestions?

[The Coolest]

To be completely honest I'm not sure what could be the cause for this problem. What I can suggest as a workaround, is to go to "Scheduled tasks" and add a delay to Core Temp's task. Maybe Core Temp is trying to load together with something else on your system and therefore causing the delay, but if you start it a little bit later, the conflict may not occur and everything will become smooth again.

[SClemente]

Thanks for your honesty. I truly think debugging software issues is part science, part art, and part luck.

I tried a few alternatives based on your suggestions.

First, in Task Scheduler I set Core Temp to auto load during startup, rather than logon. That did not work at all. Core Temp never loaded, so I switched back.
Second, in Task Scheduler (under the General Tab), my Core Temp was configured for Windows Vista, Windows Server 2008, rather than Windows 7, Windows Server 2008 R2 (that's the way it installed). I changed it to Windows 7.
Third, in Task Scheduler (under Triggers/Advanced settings), I changed the "Delay task for" to 1 sec, 3 secs and 10 secs, but so no impact on the loading time.
Fourth, in Task Scheduler, I also tried delaying the launch of Windows Sidebar, thinking the gadgets might be slowing things down, but that also had no impact on anything.

It's all very strange indeed. The delay in Core Temp loading does not appear to slow anything else down and I can open programs, but it just all seems odd. Apparently, no one else has had this issue.

Regards,

[The Coolest]

Well I tried to track what happens when Windows 8 starts off a slow HDD with Core Temp and tracked the files loaded with Resource Monitor.
The best guess is that although Core Temp itself is a pretty small application it uses a lot of other system components and since it's their first start maybe that is the reason it's taking such a long time.
If you don't use the 'Remote server' part of the program (for Android monitoring), I would recommend disabling the plugins, this may make a difference.

[SClemente]

I'm actually on Win7 64-bit Pro. I don't have any plug-ins and nothing is linked for Android monitoring. I'm going to uninstall the gadgets one-by-one, leaving "All CPU Meter v4.5" and "Core Temp" to the end and see what happens. I'll report back.

[SClemente]

Just ran a full test on gadgets and Core Temp with following results. In each case I turned off a gadget, rebooted, timed Core Temp. Then I uninstalled the gadget, rebooted, and timed Core Temp.

Turned off Network Meter, Drives Meter, GPU Meter. Core Temp took 64 secs to load.
Uninstalled Network Meter, Drives Meter, GPU Meter. Core Temp tool 64 secs to load.
Turned off All CPU Meter. Core Temp took 44 secs to load.
Uninstalled All CPU Meter. Core Temp took 44 secs to load.
Turned off Core Temp gadget. Core Temp took 44 secs to load.
Uninstalled Core Temp gadget. Core Temp took 44 secs to load.

All of the above tests were with Core Temp delayed 10 seconds in Task Scheduler. I then removed any delay in Task Scheduler, rebooted and Core Temp still took 44 secs to load.

[The Coolest]

I'm talking about plugins in Core Temp, as it usually comes pre-installed with the Remote Server plugin.
Try unchecking plugins and see if that helps. Although even if it doesn't, then my previous post is still probably the only explanation I can give on why it takes so long for Core Temp to start.

Uncheck it:

[SClemente]

I understood what you meant about Core Temp plug ins. They were never enabled.

Can you provide me with a list of the other resources CoreTemp is using so I can determine what might be loading slowly and slowing down CoreTemp?

[The Coolest]

They are basically Windows DLLs. There isn't really anything you can do to speed up the time it takes Windows to load all the its necessary components into memory, I think.