I reviewed the data summaries you've posted at the top of this blog and can only point out one obvious thing I noted.
There is a strong and consistent 24-hour cycle in the baseline scala-2 performance data sets ( you've referred to them as 'context' ). This makes sense because most games are played most often during the same period of each 24-hour cycle.
Since resources are going out of control on the same 24-hour cycle, and presumably at the time of peak resource demand, one's 'spidey sense' would suspect the overall system has not been properly configured for handling peak load.
Is the server 'thrashing' for instance, having run out physical ram and is now just dead-in-the-water jamming the busses with page-swaps ?
If this is complete nonsense, please ignore, but I thought it might be worth a mention ...
There is a strong and consistent 24-hour cycle in the baseline scala-2 performance data sets ( you've referred to them as 'context' ). This makes sense because most games are played most often during the same period of each 24-hour cycle.
Since resources are going out of control on the same 24-hour cycle, and presumably at the time of peak resource demand, one's 'spidey sense' would suspect the overall system has not been properly configured for handling peak load.
Is the server 'thrashing' for instance, having run out physical ram and is now just dead-in-the-water jamming the busses with page-swaps ?
If this is complete nonsense, please ignore, but I thought it might be worth a mention ...