About handlering all `num` of execution about aws-lambda-power-tuning HOT 5 CLOSED

@alexcasalboni
Thank you very much for your prompt response, and I apologize for the lack of confirmation input parameters.
I successfully executed "parallelInvocation": true setting and mesured optimal memory.

from aws-lambda-power-tuning.

Hi @Toyo-Daichi, thank you for reaching out :)

I understand that your function needs to run for almost 15 minutes, every time. And this becomes a problem with num>=5 because the overall execution time for the entire workflow is 15 minutes too.

Have you considered using the input parameter "parallelInvocation": true? That way, all your functions will be invoked in parallel and they can run as long as the overall workflow.

If the functions are operating on the same ETL data (input or output), I would suggest modifying the business logic to write into a "random" location to avoid conflicts between different invocations.

Would that work for your use case?

from aws-lambda-power-tuning.

@Toyo-Daichi super 🚀 I'm glad we solved the problem quickly 😄

Out of curiosity, what was the optimal memory? Could you share the visualization URL with me?

from aws-lambda-power-tuning.

@alexcasalboni
Thanks for your interest! The result is this URL.

Thanks to your application, I verified that if we can allocate memory above a certain border*, the performance will not change much. *If lower than the border, the job failed.

from aws-lambda-power-tuning.

Thank you for sharing, @Toyo-Daichi 🙏 That makes sense!

from aws-lambda-power-tuning.