You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it correct that in using LambdaClient invoke(), the whole payload is handled by a single Lambda instance? Or will it scale, dividing each record of the Payload into single lambda instance?
In my particular case, I have thousands of images to process and would like to send 100 at a time, never really overloading the number of Lambda instances created. I had planned to do this using concurrency with Guzzle Pool. However, that option doesn't seen to exist in the LambdaClient. Which, means I would need to create the signature manually.
Or, is there something I'm missing? I'd appreciate any feedback on the issue.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Is it correct that in using LambdaClient invoke(), the whole payload is handled by a single Lambda instance? Or will it scale, dividing each record of the Payload into single lambda instance?
In my particular case, I have thousands of images to process and would like to send 100 at a time, never really overloading the number of Lambda instances created. I had planned to do this using concurrency with Guzzle Pool. However, that option doesn't seen to exist in the LambdaClient. Which, means I would need to create the signature manually.
Or, is there something I'm missing? I'd appreciate any feedback on the issue.
Beta Was this translation helpful? Give feedback.
All reactions