Keep in mind spinning up cold containers may take a little bit overhead.

This also means the lower the number, the more capacity per activation can get from the container, and the more containers are needed to finish all your jobs. In other words, it will keep sending your activations to the same container until this number is reached. Description: The max number of activations that can be sent to the same container in parallel.It is recommended to use node.js v14 for your action and a memory setting that is 256M, 512M or 1024M such that pre-warmed containers can be used without a cold start. Description: the size of the container that will run your action.

For batch processing, non-blocking calls are usually intended and you can run your process up to 30 mins per activation

Range: for web action (sync calls) - 100ms to 60,000ms for non-blocking action (async calls) - 100ms to 1,800,000ms.

Description: the max time that your action takes to run, otherwise 504 (timeout) would be returned.

Please note it’s not mandatory to define those settings before you can get the auto-scaling but having a better understanding and setting them with proper values based on testing with estimated loads would definitely help drive your application to success. Notice there are a few settings under limits.

Adobe app builder