For matchmaking wouldn’t you want to prefer people having waited longer over people just having joined the queue
Not sure the word “queue” is the right word in that context.
Users are not really waiting in line, they are not really waiting anything.
It’s more like at some point we have an X amount of users online, ready to play a certain game, and as a user whether there’s 100_000 or less of those, I want to see a random 100 of those displayed in a list that I can scroll through .
Therefore, I keep track of all those guys at all time and remove them either when they disconnect or they have already found a partner to play with.
It’s more a status tracking across different games and levels(beginner, good, high).
Also would there really be a million people waiting in the queue or rather be a million people playing?
It could be a million users, some of them might look at the search result and scroll through it for some time (minutes) before they find someone they want to play with.
It’s difficult to predict how fast the number of users would decrease.
It depends on user’s preference and how “good” the result of the search is.
Once again, that’s why I want the result to be as different as possible for everyone.
So I guess sometimes it could be really fast to decrease and sometimes it could stagnate for some time
If you form couples quickly enought the queue might stay at a reasonable size
Well if I manage to return users list fast enough and shuffle enough so that users don’t see the same users on their screen, I definitely have a higher change to create couple faster, but as I said, then the ball is on the side of the user looking scrolling through the results returned.
If he’s not please with it, he could still click “search” again and see another set of random users.
that’s basically the goal
