Parent Previous Next



New Tabs

Tab changes

"Job Log"

Sort mode

There is a new sort mode for the rrClient render logs at the bottom 

Client Stats

Some statistics for all clients that have rendered on the job.

Frame Table

RR 8 and RR 9 have these two information sources regarding frames rendered:

1) There is the Servers Job Log, sorted by time
    The rrServer saves a log with all informations like frames send, job crashes, job aborted.
2) Then there is the Clients Frame Log (Named in RR8: "Frames rendered")

    The client collects some information while he is rendering frames like CPU, GPU and memory usage.

The new "Frame Table" joins the information about frames from these two tables.

The table is sorted by frame (by default).

Example usage cases:

  • Right-click to open the render logfile of a specific frame.
  • Detect if a frame was started multiple times as you see two rows of the servers job log.

Job Performance

This page uses the information from the servers job log and mostly the information from the Clients Frame Log.
The Job Performance page has three parts:

1) A bar that shows you visually how often a job was send and how often these render crashed or aborted.

2) While a job is rendering, it shows you some stats about the cliens that are rendering.

  • Segment size (How many frames are send to a client)
  • CPU usage Min/Average/Max
  • Memory usage Min/Average/Max

This section has some bar graphs that show stats that have been collected 5 times during the render of a frame.

  • Segment size (number of frames send to a client at once) and their render time.
  • Frame Time
  • Highest CPU usage
    The Client collects the CPU usage 5 times during a frame. This section takes the highest peak during a frame.
    It can be that a frame has used 90% CPU for a few seconds and all of the other render time 1%.
    For this information we are interested in this 90% peak.
    It can show you the maximum number of cores that are supported by the renderer.

  • CPU time used for a frame
    This information is the average CPU usage for a frame.
    If the average CPU usage is very low, it might be caused by a long frame pre-processing time.
    Or it might be caused by a slow texture load or not enough memory to load all data at the same time.

  • GPU time used for a frame
  • Memory usage

"Job Info"

"Job Settings"

"Global Info":

Job Table

Client Table