Search is based on keyword.
Do not search with natural language
Ex: "How do I write a new procedure?"
Op Cook Profiling
A Profiling mode exists in Katana. When launched in Profiling mode, Katana can generate reports on Op cook times within profiling sessions. Cook times are aggregated per Op instance, per location. These reports can help in pinpointing slow areas of the Op tree and scene graph.
The profiling is low overhead to minimize its effect on cook performance and the more computationally demanding data aggregation is performed at the end of the profiling session.
Note: The timing report files produced can be extremely large, of the order of gigabytes. As a guide, note that typically one line of information is produced per Op instance, per scene graph location at which it is cooked. This is why we recommend you use profiling mode selectively when measuring cooking times, and not during normal production usage of Katana.
The following command-line options allow you to set the specific Profiling mode you want to use, or to specify a directory where profiling reports are written:
• --profile - launches Katana in Profiling mode,
• --force-profile - launches Katana in Profiling mode and starts a profiling session immediately on launch,
• --profiling-dir=[DIR] - specifies the directory where the profiling reports are written.
Note: For more information on command-line launch modes in Katana, see Command-line Interface
Learn the basics of beginning and ending a profiling session in Katana.
An overview for profiling renders in Katana.
A guide for creating and analyzing profiling reports.
Sorry you didn't find this helpful
Why wasn't this helpful? (check all that apply)
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.
Thanks for taking time to give us feedback.