Congratulations Steve to you and your wife on the new little bundle of joy.

May he sleep through the night and be a joy always!!

Just think before you know he'll be asking for the keys to the car.

How fast they grow up.

Congratulations again!!!

Indeed we are. Big project, so I had to pull the WCG agent off the farm for now, as we need max power right now. Hopefully once this project is over I can go back to crunching as usual, but meanwhile I'm back to 1/2 power (admin machines only).

Our SFX shots are generally used in trailers, rather than the film itself, although there is some cross-over. I'd rather not advertise on these public forums but if I catch you in the chatroom sometime I'll shoot you a link to our company's website so you can see some of our stuff.

Thanks for the explanations on how the agent switches tasks.

Now for my next query(s)...

I recently had the agent off for awhile and when I put it back up, the “Task Run Time” was greater than I thought it should have been. It seems as though the Task Run Time is reporting the elapsed CPU run time since the task has been acquired rather than the amount of time actually spent running the task?

Another question I have is about the relationship of the heavy hitters to those (like me) who just have one old pc plugging along with the cpu clock speed being determined by how fast the hamster in the squirrel cage is running, an Ethernet card built out of spare car parts, and a steam powered monitor. While I see the big guys racking up the mega points, I wonder how much the rest of the smaller users are contributing to the big picture. Does anyone have any stats on that?

Thanks,
- dc

Hi All, Thanks for kind words. Be in touch later.

Task Run Time is the total wall clock time the task has been running. It's not CPU time, or absolute wall clock time since the task was downloaded. Thus the amount of time it takes for the same workunit to complete on the exact same hardware will vary depending on the usage of that computer. They will have taken the exact same amount of CPU time to complete, but differ in the amount of wall clock time. That's just the way the UD software measures it. It's also why we customized our Agent to correctly state it as "Task Run Time" as opposed to "Task CPU Time" as the UD software incorrectly lists it. The same can be said of "Total Run Time", as it's the accumulation of "Task Run Time" for each completed workunit.