Not sure if this issue should go here in st2 or in StackStorm-Exchange/stackstorm-aws
There are 3581 (ish) actions in the AWS pack, and when it's installed, many things perceptibly slow down (actions page & workflow designer in the UI, registering actions, etc).
I'm just curious if others are experiencing this issue and what can be done about it to help speed things up for us when we use the AWS Pack.
I believe our box ha 8 cores. Is it possible we're not utilizing them all or something?
@mickmcgrath13 This is a known problem and we're in the middle of trying to re-work the AWS pack to have far fewer actions. The problem is how to do this without "pulling the rug" out from under the current users - it's a very popular pack.
There should be some PRs and/or issues on that repo soon to outline the plan, I'd suggest hanging around there for news. In the meantime, some have seen success with increasing RAM or CPU allocations.
Just repeating a note, similar to https://github.com/StackStorm/st2/issues/3697 and https://github.com/StackStorm/st2/issues/3686 issues, I think that StackStorm _should_ be able to handle thousands of actions in pack(s) by design without a problem.
It could be more packs with hundreds of actions installed, which in summ several thousands of items.
So IMO it's not the AWS pack guilty, but the root cause has to be fixed: we just need to identify the bottlenecks and optimize the entire StackStorm performance when dealing with bigger packs (which wasn't really a big focus before).
Thanks for writing out my thoughts @armab :P Saved me some time :)
(..that thought also solidifies this issue's belonging in st2 instead of the aws pack's repo)
Most helpful comment
Just repeating a note, similar to https://github.com/StackStorm/st2/issues/3697 and https://github.com/StackStorm/st2/issues/3686 issues, I think that StackStorm _should_ be able to handle thousands of actions in pack(s) by design without a problem.
It could be more packs with hundreds of actions installed, which in summ several thousands of items.
So IMO it's not the AWS pack guilty, but the root cause has to be fixed: we just need to identify the bottlenecks and optimize the entire StackStorm performance when dealing with bigger packs (which wasn't really a big focus before).