- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hi,
I’d typically look at these items (not in any order really)
1 - Add logging to your lambda to record time stamps, to understand where the time is lost.
2 - Check why the endpoint taking Xs to reply. What is it doing, can that be optimised in anyway. Can it be amended to provide the data you need sooner and then run additional steps.
3 - Is your lambda sized correctly, https://dev.to/byrro/how-to-optimize-lambda-memory-and-cpu-4dj1
4 - Is time lost in your lambda, can this be optimised, refactored to a different language (extreme IMHO)
Playing music during the invocation is not supported.
Invoking async from a Connect point of view will work.
Maybe adding the lambda at the start before prompts will improve the customer experience.
Thanks
Dan
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa