When building a game server intended to accomodate large numbers of simultanous games (e.g. table card games), where the server manages lots of tables and each table has up to a small handful of users, what metrics are most useful to collect and why?
Tell me more
×
Game Development Stack Exchange is a question and answer site for
professional and independent game developers. It's 100% free, no registration required.
|
|
For metrics regarding the gameplay I'd suggest simply recording a full history of each game, with each action timestamped. As card games tend to be fairly slow paced that shouldn't generate too much data and it lets you do any other analysis of the games you want to at a later date by just using that history data. |
|||
|
|
Since you're already tracking the state change of the game for each move, I don't see what else you might monitor in relation to the "game" itself; however, many commonly tracked server metrics include:
Depending on your server platform there are different tools to monitor this data. The reason to monitor these, is because they directly impact performance and they are all finite resources on any given server. If you start maxing one of these out, you need do either, add more of that resource, re-write some of your application to work within the limits on your server. |
|||
|
|
