Hi, I've got a 650 frame comp with 200+ Read/DeepRead nodes, and am getting frequent UI lag (a couple of seconds of stuttering) when I create a node or change a knob value with no viewer attached. Or even toggling cached views. I've seen a worse version of this kind of thing a few years ago but that was more to do with callbacks gone wild in the plugin path.
After checking the autosave path/frequency and any custom callbacks in the plugin path, I ran import callbacksTrace in the script editor so I could see the low level stuff. As expected, filenameFilter() is running a zillion times all the time, but in this case it seems that the fact I have 130000 individual frames is causing a slowdown since it's iterating over all those frames on onCreate() and knobChanged(). Basically the UI lag corresponds with filenameFilter() appearing in the shell then I get interactivity back. That plus network overhead when there's a lot of rendering seems like the culprit. Any ideas about whether there's a python-based solution to speed things up? I'm also going to localise in the Read to see if that helps, but will need to do that overnight until there's a BG way of doing that. Frank, I'm looking forward to trying out what you're working on at some point. I'm on Windows 7 Enterprise SP 1, maybe that's figuring in as a file system issue. I'll also email support. Thanks, Michael
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
