GMS Server Status Discussion < 10-31-2011

There are several flaws in the suggestions;

1) The process that gets the data and the process that displays the data are not connected to each other, have no awareness of each other and run independently from each other. They don't know what each other are doing and in order for them to do so it'd degrade performance.

2) The display procedure is a cross tab, there's no where to put channel by channel timing in without adding 30% more fields to the query, again, which adds yet more overhead slowing the whole thing down and making it more intensive every time someone hits it. The existing as of date is either a min per server or max (formerly the latter, currently the previous). It can't be readily compared to any other times because they aren't present in the set at the point it exists.

It really seems like a few people just aren't happy with it not doing every possible thing they could ever dream of and desire, right up to hiking itself down to Nexon HQ and slapping an exec every time lag spikes over .1.