Is waiting time in the queue counted in FlexMatch's Matchmaking Hours?

0

I'm planning to use FlexMatch as a matchmaking system for my chat app. It basically works like Omegle in which two authenticated users are matched based on its input interests. (e.g. they both have an interest to keyword "DevOps" - the two would be matched).

Since FlexMatch uses the ff below to determine its price:

  1. Number of players to be matched
  2. Matchmaking hours

It would be very expensive if queue time before a match is found is billed from the matchmaking hours. Based on how I understand the documentation, I wonder if this is indeed the case.

The rules I'm planning to set is for a user to wait 5 seconds before a match is found, if no user is found then match it to a stranger.

Renz
已提問 2 個月前檢視次數 119 次
1 個回答
0

Hello! Billing will occur during a portion of the matchmaking time, but not during the entirety of it. Billing occurs only while potential matches are being searched for. This does not include the time during which players are grabbed from the queue to be matched.

Additionally, it's important to note that "Matchmaking Hours" can be influenced by the complexity of the matchmaking rule set that is provided by the customer. If a rule set is more complex, and there are more rules for creating matches, matchmaking will potentially take longer and result in more "Matchmaking Hours".

AWS
已回答 2 個月前
profile picture
專家
已審閱 2 個月前
  • I see, thank you for that. What I mean is let's say the matchmaking status based on DescribeMatchmakingCommand (from SDK) is Searching...this status has been going on for 30 seconds. Does that mean I'm also billed for whole 30 seconds, because if this is indeed the case that's very expensive for cases in which a user cannot find a match.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南