i have many messages on STDOUT when render worked. its warning and plugin messages.
local console buffer fast view that messages (via cmd.exe), but slave to slow print it in our console.
cmd.exe print all messages about 2 minute
slave print it about 20 minute
and its mot many messages! sometime render generate 10k and many strings in console and render wait when slave get and print new string…
how i can speed up console into slave?
if console have few strings into slave - maybe it speed up all work? if slave clamp messages and now allocate new memory for many strings…
The slaves handle large amounts of stdout much better in Deadline 4.0, so if you can upgrade, that would be the best solution.
If upgrading isn’t an option right now, then you could try reducing the verbosity level when submitting the jobs. I believe it defaults to 5, so maybe try setting it to 1 or 2 to see if that helps speed things up.
when verbosity 1 or 2 - deadline not show render progress and not finish job. mental ray not talk to slave when end render and slave hold frame forewer
That’s strange. I can understand that Deadline wouldn’t show render progress (since mental ray isn’t printing any progress out when verbosity is low), but that should not affect whether or not the render finishes. Deadline isn’t looking for a particular message to tell it that the render finished successfully, it’s just waiting for the mental ray command line job to exit.
Here is a description of each verbosity level for mental ray:
So maybe try setting it to 4. This way, you should still get progress reporting, and hopefully ignoring the informational messages reduces the stdout enough.