Github user roshannaik commented on the issue:
- Thanks for giving it a spin and posting the numbers. The higher CPU in
multi-worker mode is not something I have seen before. Will take a look. Can
you please share the cmd line that you used ? Were all 4 workers on same host ?
- Plan is to rerun the suite that was previously published and see if any
regressions were introduced due to recent changes and the rebasing .. which i
think introduced about 300 or so commits since the last perf run. Will do this
once we have
-**Side Note:** If you run TVL again, do pay attention to the latency on
the UI. TVLs report does not seem to be including the actual latency.
Will quash the commits and refresh this PR so that it can be committed.