Optimizing for speed
On this page, a few strategies are presented for making a render on Lambda as fast as possible.
Higher concurrency
Generally, a lower value for framesPerLambda will result in higher concurrency and therefore an opportunity to finish the render in less absolute time. At the same time, more overhead will be produced, making the render more expensive. You will also experience diminishing returns, and adding too much concurrency can make the speed slower because the overhead of orchestrating many Lambda functions outweigh the gains.
See the Lambda Concurrency page for more information.
More memory
Adding more memory on Lambda will also scale up the CPU power on Lambda proportionally, therefore making the render faster. At the same time, the cost also linearly increases with the memory you add.
concurrencyPerLambda property
The concurrencyPerLambda property in renderMediaOnLambda() allows you to open multiple browser tabs in a single Lambda function, therefore opening an opportunity to do more work at once. If the Lambda function is too busy, increasing the concurrency might also be counterproductive.
Make the render more performant
See the general performance tips which also apply to Lambda.