Not sure if this is a bug, or just a fact of life.
When utilizing the Actor COMP Flex feedback TOPs I see a pretty big hit to my whole system. This seems to scale with how strapped the rest of my network is for resources, which makes me wonder if the performance monitor’s line for the flex solver is catching other things. When i look at Perf. Monitor, I am seeing the flex solver’s supposed cooktime increase greatly when I have TOPs in the feedback position and velocity pars, as well as a general performance drop.
I am utilizing the work I am doing to feed those TOPs in other parts of the system, so that stuff is all still cooking even if not being fed back in.
So main question is, is it a “bug” or an unavoidable consequence of using the Flex feedback feature?
Will try to prep a file to demonstrate, but wanted to float the question in case Eric perhaps can shed light generally.