Latency Optimization in Argo Workflow with HTTP Template Execution

[hyeongwooo]

We have currently configured the workflow using two steps with HTTP templates,
and set it up so that the workflow is triggered by the Argo Sensor upon receiving an event.

Based on the event log (first image) and the workflow resource log (second image), it currently takes approximately 9 seconds for the init container and main container to be created and the process of completing and reporting to the workflow controller

We are wondering if there are any ways to reduce this latency, and if there might be alternative design approaches to consider.