Quote:
Originally Posted by jnikkir
Okay wow, thank you SO MUCH for doing this! I installed, manually CTRL+Tabbed through my VM views with no VL open, then clicked though my VL tabs (which have Action Chains associated w/ them), to compare the speeds between two. It actually does look like maybe the Action Chain switches have the biggest lag? I could have sworn there wasn’t much difference, but if I’m reading this right, it looks like there is. Maybe I've been looking for the cause of the lag in entirely the wrong place...
|
When you were switching Views, the longest time (up to ~1.5s) is during
self.gui.library_view.apply_state(...) , as expected. That's still a bit longer than I'd honestly expect, but not insanely so.
When doing VL changes, it looks like Action Chains is calling VM's
apply_column_and_sort() instead of
switch_view(), which I would have expected.
For one thing, it means that the "7.1" time can't be trusted--VM is resetting the time at the start of
switch_view(). What you see there for 7.1 includes all the wall-clock time passed since the last interaction. You may be right, but you can't trust this output to tell you.
(Presumably Action Chains is also reading the VM config data needed to call
apply_column_and_sort()? I don't know what it does...)
I'm not usually involved in debugging whole libraries. Is it appropriate to ask for a zipped copy of the library to look at? If it's not too private or too copyrighted, that is.