- Wed Jun 24, 2009 9:42 pm
#302775
I have noticed in watching the CPU and network activity on my render nodes that there is a lot of idle time.
The Server console will say it has achieved a new sample level, the CPU usage will drop down to idle, and after writing the new MXI to the server, the network activity returns to idle, and then it just sits there for awhile...and sits...and sits....
Then after a while the CPUs suddenly pick up and it starts all over again. CPUs spike for awhile, then they drop, it writes, and it waits.
Why does MXCL manager take a coffee break after each sample level? Seems to waste an awful lot of time.
The Server console will say it has achieved a new sample level, the CPU usage will drop down to idle, and after writing the new MXI to the server, the network activity returns to idle, and then it just sits there for awhile...and sits...and sits....
Then after a while the CPUs suddenly pick up and it starts all over again. CPUs spike for awhile, then they drop, it writes, and it waits.
Why does MXCL manager take a coffee break after each sample level? Seems to waste an awful lot of time.
mo cores, mo problems
- By Forum Moderator
- By hwolfejr