In 5.1 I got stats per frame:
hobbes:~ frank$ /Applications/Nuke5.1v4/Nuke5.1v4.app/Nuke5.1v4 -Vfx /tmp/test.nk 1,10 Nuke 5.1v4, 32 bit, built Apr 3 2009. Copyright (C) 2008 The Foundry Visionmongers Ltd. All Rights Reserved. Loading /Applications/Nuke5.1v4/Nuke5.1v4.app/Contents/MacOS/plugins/init.tcl Loading /Applications/Nuke5.1v4/Nuke5.1v4.app/Contents/MacOS/plugins/init.py Loading /Applications/Nuke5.1v4/Nuke5.1v4.app/Contents/MacOS/plugins/setenv.tcl Loading /Applications/Nuke5.1v4/Nuke5.1v4.app/Contents/MacOS/plugins/CheckerBoard2.dylib Loading /Applications/Nuke5.1v4/Nuke5.1v4.app/Contents/MacOS/plugins/jpegWriter.dylib Writing /tmp/0001.jpg Writing /tmp/0001.jpg took 0.01 seconds Writing /tmp/0002.jpg Writing /tmp/0002.jpg took 0.01 seconds Writing /tmp/0003.jpg Writing /tmp/0003.jpg took 0.01 seconds Writing /tmp/0004.jpg Writing /tmp/0004.jpg took 0.01 seconds Writing /tmp/0005.jpg Writing /tmp/0005.jpg took 0.01 seconds Writing /tmp/0006.jpg Writing /tmp/0006.jpg took 0.01 seconds Writing /tmp/0007.jpg Writing /tmp/0007.jpg took 0.01 seconds Writing /tmp/0008.jpg Writing /tmp/0008.jpg took 0.01 seconds Writing /tmp/0009.jpg Writing /tmp/0009.jpg took 0.01 seconds Writing /tmp/0010.jpg Writing /tmp/0010.jpg took 0.01 seconds Total render time: 0.11 seconds Allocated 3.54MiB, 0% of usage limit of 1GiB, sbrk = 91MiB. free_*() calls: 0, new_handler() cleanups: 0. CheckerBoard1: 3.52MiB 640x480 rgb 100% w 38400 hobbes:~ frank$ On Apr 28, 2011, at 11:36 AM, [email protected] wrote: > Does anyone have any ideas if this worked at any point, just to see if > I have to clarify my ticket as a regression or a feature request. > Doesn't seem to work all they way back to 5.3. Thanks. > > On Wed, Apr 27, 2011 at 2:27 PM, [email protected] > <[email protected]> wrote: >> I've sent a ticket, thanks. >> >> On Wed, Apr 27, 2011 at 1:15 PM, Frank Rueter <[email protected]> wrote: >>> wow, that is annoying. I'm sure it used to show render times per frame in >>> previous versions when using verbose mode (I haven't checked in ages >>> though, so don't know when that disappeared). >>> I guess you could try afterFrameRender callbacks to build your own custom >>> system, but this should definitely be reported as a regression >>> >>> >>> >>> On Apr 28, 2011, at 6:40 AM, [email protected] wrote: >>> >>>> Hi, just wanted to check what you guys use to check render times, >>>> performance and metrics (I need to test on the local machine on a gui >>>> session). Verbose mode does not seem to report it, and -P mode doesn't >>>> either (only individual nodes, it seems). I have tried to use timeit >>>> through python on a nuke.execute, but I haven't been able to make it >>>> work. Your ideas are much appreciated, thanks. >>>> _______________________________________________ >>>> Nuke-python mailing list >>>> [email protected] >>>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>> >>> _______________________________________________ >>> Nuke-python mailing list >>> [email protected] >>> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python >>> >> > _______________________________________________ > Nuke-python mailing list > [email protected] > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python _______________________________________________ Nuke-python mailing list [email protected] http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
