Slow Webhook response performance + High CPU

[jan]

Yes, the advantages are actually explained in the same topic here:

WorkflowRunner use 'fork' to create subprocess , when WebHook always receive request, will make many subprocess , and CPU usage so high

Yes, that is right. It got implemented like that on purpose. By starting multiple processes it makes sure that if multiple workflows run at the same time they use all available CPUs and do not block each other (which would be a big problem for CPU intensive tasks). Additionally, does it also make sure that if one execution crashes, all other executions and especially the main process run uninterrupted. Honestly, am I also not the biggest fan of it. Less however because of the CPU usage but more…