This is RenderMan 21 Documentation you are viewing. The Rmanwiki home page will redirect you to the current documentation.
The Limit Counters tab displays the the tally of the current limit counts in effect in the engine.
The counters tab can be limited to only displaying counts associated with formal limits, as defined in the limits.config file.
The Site value is the site-wide or global limit as defined in the limits file. You'll see in the example above there are 5 defined global limits: limit10 == 10, limit15 == 15, limit5 == 5, limittest==50, and prman is currently unlimited. In this picture none of these limits are currently in effect.
Clicking off the Show only limits in config file checkbox will present ALL the current limits. Besides the config-defined limits, as mentioned above, there are limits that are constructed by the engine, on-the-fly. These limits come from:
- The name of the running command, i.e. prman
- The name of the user, such as rdavis
- The service key, i.e. pixarRender or RMSRibGen
- Any tag defined in the job script, like intensive or Prod 6
As you can above, there are currently 160 running tasks. All 160 tasks were launched with the service key pixarRender. Out of these tasks, 129 are running jobs from rdavis, while 31 are running jobs from ratbuild.
The 31 ratbuild jobs are all running pysleep tests, while rdavis' jobs are not displayed in this image, as they were below the image cut-off point.