- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello, did you root out the possibility of lambda cold start? Or can you provide some ticket ids & rough time & region so we can take a closer look?
Had a very busy couple of weeks here, thanks for responding and we'll appreciate if you'll take a look.
Ticket ID: DefaultTournamentDefinition-3--7caa6778-e1d9-4d0a-a246-cc3b77a75a4c Region: eu-central-1 unix seconds of startMatchmaking returned success 1646420747 our lambda was invoked by event bridge for "MatchmakingSearching" and "MatchmakingSuccess" at unix seconds 1646420755
Regarding the possibility of a lambda cold start, I'm not seeing why a cold start would take 8 seconds in our case. Also, we can have a ticket take this amount of time followed by multiple tickets that take this amount of time. Also there are no long running / network operations happening in the matchmaking event listener's global scope.
Just tried using SNS -> SQS -> Lambda for matchmaking notifications with similar results. Always a delay of at least about 5 seconds before receiving even the first "MatchmakingSearching" event after calling startMatchmaking.
Contenus pertinents
- Réponse acceptéedemandé il y a 2 ans
- demandé il y a un an
- demandé il y a 7 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a un an