How is this done among the devs? Are you guys using valgrind/similar? Any information would be appreciated!
For a first pass, I suggest using the arnold profiler:
Note you can add the profiling instrumentation to your own code so you can measure where time is being spent. This will let you know what code block in your code is taking the most amount of time.
After that, Apple Instruments (for OSX), perf (for linux) or vtune/visual studio (for windows) can be used to see low level details of where your code is spending time (this instruction was 1.3% of the time) and why it might be slow.
Just an hint. Before going to profile is good practice to formalize your code in unit tests that can be run without the shader/plugin dep. First because it's almost impossible to profile a shader lib with ie. vtune/perf, second because probably ai.lib can't be run in a free environment (could be locked to Arnold and also it looks like there ain't a debug version).
This is the place for Arnold renderer users everywhere to ask and answer rendering questions, and share knowledge about using Arnold, Arnold plugins, workflows and developing tools with Arnold.
When posting questions, please be sure to select the appropriate Space for your Arnold plugin and include the plugin version you are using.
Please include images, scene and log files whenever possible as this helps the community answer your questions.
If you are looking for Arnold Documentation and Support please visit the Arnold Support site.
To try Arnold please visit the Arnold Trial page.Bottom No panel present for this section.
11 People are following this question.