1 Answer
- Newest
- Most votes
- Most comments
0
A few things to consider:
- You say it is not a cold start issue. Are you sure? Check in your CloudWatch Logs group. The first invoke in each Log stream is a cold start, the rest are the warm starts. Can you correlate them? I saw on SO that you say that the issue goes away if you first prime the function with a small input. This actually points to some sort of cold start that in the first invoke it requires more processing.
- You allocated 10GB to the function, but you are only using 800 MB, this is an enormous waste, unless your code is multithreaded and can utilize more than one core. Otherwise, reduce the memory to 1760MB.
- Yes, I have checked that it is not a cold start. And even if it was a cold start, how can priming speed up a cold start?
- The function becomes faster proportionately with increasing memory. I would increase it further if I could.
Relevant content
- asked 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 19 days ago
- AWS OFFICIALUpdated 4 months ago