Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
Why is my Lambda concurrency limited to 30 instead of 1000
I trigger my Lambda function for 10,000 times by uploading images to S3.
for each in imagelist:
NAME_FOR_S3=+str(each[0])+'_'+str(each[1])+'.png'
LOCAL_FILE=mypath+NAME_FOR_S3
counter=counter+1
Lambda takes about 20sec to analyses each image. I have reserved concurrency of 990 for my Lambda function. However, during the actual run, the "total concurrent executions" is about ~30 at most. (
How to make the "total concurrent executions" bigger so my computation runs faster? Thanks
- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi,
To really test the available concurrency, I would try to eliminate the time of the upload itself. So, to achieve that, I would first upload my images into a first bucket and then copy from first bucket to a second one where the trigger is defined. And btw, I would use S3 sync command across the 2 buckets to be faster than individual copies of files to give maximum chance to concurrency to increase.
In your current setup, the time to upload the image may be the factor limiting the concurrency.
Best,
Didier
Approximately how long does it take to upload all the 10,000 files to S3?
With my image analysis code (which takes 20sec to run for each image), 2 hours Without that code (so each Lambda invocation takes only about 30ms.) 1.35 hours
Invocations without the analysis code is ~360 compared to about 220 with the code
Contenus pertinents
- demandé il y a 3 ans
- demandé il y a 6 mois
- demandé il y a 3 ans
- AWS OFFICIELA mis à jour il y a 9 mois
Indeed, this is a good and easy way to pinpoint the bottleneck. I also agree that the rate at which files are arriving in the bucket being the limiting factor would be the most obvious explanation.