Re: [K3d-development] Document Loading Times
Brought to you by:
barche
From: Joaquin D. <hoa...@ya...> - 2008-09-28 22:04:34
|
Timothy M. Shead wrote: >> Obviously the problem was on the connections between properties since removing >> them from a K-3D document change the times on an unpatched K-3D. > > No question that this is a problem that needs to be solved, but this may > be a sign of a deeper issue. Simply setting property dependencies > should not take this much time - either storing undo/redo information > when properties change is out-of-control (doubtful), or the pipeline is > being executed, which in-theory should never happen. It would be useful > if you could capture some information on whether this is the case - you > can do a little hacking on the serialization code so that it listens to > the pipeline profiler interface and prints execution times to the log - > again, there shouldn't be any, but probably is. I made first a simple test and this limes seem to be the problem. // Synthesize change notifications for every property whose parent was set ... for(dependencies_t::iterator dependency = Dependencies.begin(); dependency != Dependencies.end(); ++dependency) dependency->first->property_changed_signal().emit(Hint); Even if i change the last line to dependency->first->property_changed_signal().emit(0); There is a lot of delay on loading. Also seems is not the amount of plugins only, but the type, since i tried 200 BulgePoints modifiers and has no effect. Maybe are the plugins that recieve hints? > See > modules/test/pipeline_profiler.cpp for some sample code that could be > temporarily copied to modules/k3d_io/k3d_document_importer.cpp for testing. After all, should I made this test to see if the process is eating CPU inside the node evaluation? Or the information above gives enough detail? (ill be trying to do it anyway) Cheers! Joaquín |