remove some deepcopy to speed up workflow conductor - #256
Conversation
remove 3.6 tox for now
|
The use of 'latest' is causing my tox unit testing to fail it appears. I also had to disable python 3.6 for now. |
set ubuntu-20.04
stevedore is not working in the python 3,8 unit tests
|
@m4dcoder can you please take a look at this python 3.8 test failing. It looks like stevedore is not able to find the native, mock plugins to run the tests in python 3.8. |
|
I did some testing with st2 and this definitely breaks with-items no longer report failure to the parent workflow. |
|
task render speed gain when removing deep copy for large parameters |
|
I added a micro benchmark to show how much faster it is to NOT do a deep copy. I could add it for the serialize and deserialize, but the results will be the same. Copying large objects is costly. |
|
all the 3.9 tests passed with these updates minus the lint checks). |
|
I am running this additional speed up on our internal fork of St2. It looks like ci/cd failed because black changed with their latest release. |
|
@Kami @guzzijones are we requiring the feature flag to switch between deepcopy and fastdeepcopy for this to move forward? |
|
Note, this will help with "with items" speed issues. |
@Kami is not active on this project anymore it seems
|
@nzlosh @cognifloyd please take a peak at this. I adds significant speed improvements by eliminating some deep copies. This helps with larger context objects. |
|
Anyone willing to give some feedback here? |
|
Technically I'm OK with this to be merged. As discussed mid 2024, it should be merged as part of st2 3.10. I think we should leave a release between the pymongo updates and the deepcopy change to avoid confusing any issues that may come up in the 3.9 and 3.10 release. |
|
are we ready to merge this? |
Uh oh!
There was an error while loading. Please reload this page.