Hi everyone,
I'd really like to find more in-depth technical information on render logs, I was wondering if that info is available anywhere? Really quite interested in the "OpenImageIO Texture statistics" for example.
I've found this doc, but it unfortunately doesn't go into much detail.
https://docs.arnoldrenderer.com/display/ARP/How+to+Read+a+Render+Log
The main goal is to be able to tech check assets / spot unhealthy assets and shots in terms of render optimizations etc.
Edit:
"OpenImageIO ImageCache statistics"
Thanks very much,
Andrew
Solved! Go to Solution.
Solved by Stephen.Blair. Go to Solution.
No, people usually ask about specific parts of the log, so there's answers posted in different parts of the user community. There's no "advanced render log" documentation tucked away somewhere.
But please ask and I'll do my best to get some answers...
I've edtited the main post with a couple more specific questions. For when you get a spare moment. 😉
File I/O time
Large I/O times may indicate a network problem eg very slow transfer rates
Redundant Reads vs Cache Memory
If redundant reads is large, you'll probably benefit from a larger cache. Redundant reads means tiles are flushed from the cache, and then read back in later.
Total pixel data size VS Total actual file size
OIIO (the texture cache) holds uncompressed image data, while files on disk have compressed iamge data
Tiles
If the cache is too small, you'll see more tiles being loaded, because the same tiles are loaded over and over. Check the mip counts:
| Top files by bytes read: | 1 265.7 MB ( 2.3%) 8192x8192x4.f32 example.tx MIP-COUNT [1523,1720,671,234,75,17,4,1,1,1,1,1,1,1]
If see huge numbers of reads at the higher mip levels (eg 1523 above for the 8192x8192 mip map level) then the cache is probably too smal