Hey guys,
So ive got a system that is reading as 1.6ghz instead of the 2.9 it should read. It is also rendering half as fast. All cores show up, and the other 2 systems that are duplicates of it also show at 2.9 and render twice as fast.
I have uninstalled/reinstalled the client and CPU Z reads all the procs correctly as does the task manager.
Any clue as to what might be going on?
Thanks in advance!
-Will
PS I also deleted the slave from the monitor after uninstalling client…
Hey Will,
We’ve seen this before, and the issue was that the current processor speed of the machine was somehow set lower than the max processor speed.
Deadline uses WMI on Windows to determine the processor speed. This article explains how you can use the Windows Management Instrumentation Tester utility to find the CurrentClockSpeed and MaxClockSpeed values of your processor (you’ll have to scroll down a bit):
support.microsoft.com/kb/888282
Deadline uses the CurrentClockSpeed, so if your MaxClockSpeed shows 2900, but your CurrentClockSpeed shows 1600, that could explain the problem. Give the utility a try and let us know what values you see. If you are seeing 1600 as the current clock speed, that explains why Deadline is showing this value, and why you’re getting the slower render times. Note that this is entirely out of Deadline’s control, so the machine itself would have to be “fixed”.
Cheers,
Yo Ryan,
Thanks for your prompt reply.
Unfortunately the current and max on both procs are showing 2934 (0xB76).
Im willing to do what it takes to bring this box back into line. Any other ideas?
Thanks again,
_Will
PS. I will get into bios and make sure no speed step or similar throttling is enabled…
Hmm, that’s odd. Deadline just reads that value directly from WMI, so I have no idea why the value it reads in is different than the one the WMI tester utility is showing…
If I can think of anything I’ll let you know.
Ok I did it again and its now showing 1584 (0x630). So thats the issue.
Its possible it either changed or I accidentally did the WMI on another box.
What is the fix?
Just changing the current proc speed to the max doesnt do it. Exiting and returning shows the reduced value.
Again, Ill check on bios throttling…
Thanks!
-w
SUCCESS!
Disabling EIST and C-State Tech in bios (and deleting node in deadline monitor so it could re-add) brought it back to 2.9.
Thanks for all your help Ryan!
Cheers,
_Will
Awesome! Thanks for posting the fix. I’m sure someone else will find this helpful in the future. 
Cheers,
Sigh!
Sadly even though its reading as 2.9 now, its sill terribly slow. Half speed at least.
I tested a local render to be sure its not a 3dsmax/machine issue, and it actually rendered a few seconds faster on a 3min render.
Any other ideas on how to speed up the computer through deadline?
I have uninstalled, rebooted, and reinstalled the client.
Same # of buckets, just half as fast…
Thanks for any additional suggestions.
_Will
A few seconds faster than a local render on the other machines, or a few seconds faster than a deadline render on the other machines? Also, is that 3 minutes a frame, or 3 minutes for the entire sequence? Just trying to get a better sense of the timings you’re seeing.
Note that when rendering through Deadline, the first task that a machine picks up will naturally take longer because max has to load, then it has to load the scene. However, after that first task, max will stay loaded in memory, so subsequent frames will be a bit faster.
Cheers,
Also what renderer?
Cb