We noticed that the Deadline monitor is incorrectly reporting our machine’s CPU speed on some machines and we’re curious why this is? It’s also displaying this in the Slave information tab. Attached is a screenshot of what we’re seeing.
Hello Brett,
Deadline is reporting the speed that the processor reports it is supposed to be, not the speed it’s running at(over/under clocking, underperforming hardware, etc). So if your CPU tell us it is supposed to be 2.4 Ghz, that is what we will report in the slave.
Interesting.
We noticed, however, this isn’t consistent. We have machines that are all identical in hardware configuration and all drives cloned from the same image. Some report 1.6, others 2.4…
Are there differences in the bios settings? Even if the hardware and disk images are identical, these could still be different.
Hello,
Ok, so this is my bad. It was pointed out to me that my answer was actually reversed. Windows reports the speed it is listed as, and we report as it is actually running at. I apologize for my mistake.
Just to jump in here… Deadline does not report the actual cpu speed it’s running at.
As far as I can tell here it reports the speed up the value that is listed in the windows system properties at the moment that you start the slave, and doesn’t look at the actual running frequency at that time.
I have a overclocked i7-3930k here that can run up to 4.3 ghz according to several hardware monitoring tools where windows system properties tells me it’s running at 3.2Ghz
When I have a low power plan running which sets the cpu to run at 1.4 ghz and I start the deadline slave, the monitor reports it’s running at 1.4ghz.
When I have it running at full power (4.3Ghz) and start the deadline slave, the monitor reports it’s running at 3.2Ghz (as reported in the system properties)
The only logical explanation I can think of is that deadline reads the highest frequency that the system properties tell (taken into account the cpu % set in the power plan) and doesn’t take into account any turbo multipliers that make the cpu run above the system value (or below). Plus the slave doesn’t update the cpu frequency when it changes.
It will only update the value when the slave (re)starts.
all my nodes are (slightly) overclocked to get the max performance within my available budget and all of them have the same ‘issue’ with faulty reported cpu frequencies
There are 2 nodes that have a base clock speed of 3.4ghz and at their max they run at 3.5 Ghz
In theory they could run at 3.7Ghz but the turbo has been limited in the bios.
the windows system properties reports they are running at 3.7Ghz and deadline takes over the 3.7 values and displays this in the monitor even though they only run at 3.5Ghz
i have a similar issue here at the moment…
i got different CPU speeds all the time… from 792MHz up tp 3.7GHz from different machines… all the same config…
very strange…
Hello,
To clarify this situation, in Deadline 6.2 and earlier, the CPU was reported in the slave window to be only as fast as it was running when the slave launched. This was a snapshot of the speed at that time, not a reflection of the speed of the CPU or a speed that was likely to change. This has no effect on renders, as the slave has no ability to control how much of a CPU’s power is used, only the cores that are used. In Deadline 7 this will be better, as the speed will update as the slave runs. I hope this clarifies.
