Katana 3.5v5 docs:

Profiling Renders

Renders are executed by the renderboot sub-process launched by Katana's katanaBin main process. This means that render processes have their own instances of the Geolib3 Runtime that can be profiled as well. Any renders launched in the standard, Interactive Katana mode, as well as the Shell and Script modes during a profiling session (after StartProfilingSession() and before EndProfilingSession() on Katana's main Runtime) are profiled and produce their own profiling reports at the end. In Batch mode, the render is profiled if the --force-profile or --profile options are used.

Did you find this helpful?

Yes No

Sorry you didn't find this helpful

Why wasn't this helpful? (check all that apply)

Couldn't find what I was looking for

Instructions are confusing

Instructions didn't work

Title is misleading

Content is out-of-date

The translation is poor

Thanks for your feedback.

If you can't find what you're looking for or you have a workflow question, please try Foundry Support.

If you have any thoughts on how we can improve our learning content, please email the Documentation team using the button below.

That's great!

Thanks for taking time to give us feedback.

Katana 3.5v5 docs: