Graph smoothing

This commit is contained in:
Cryptkeeper 2015-12-18 02:17:39 -06:00
parent 7e4d3c1f58
commit d07a315208
3 changed files with 12 additions and 8 deletions

5
app.js
View File

@ -86,7 +86,10 @@ function pingAll() {
// Push it to our graphs.
var timeMs = util.getCurrentTimeMs();
if (!lastGraphPush[network.ip] || timeMs - lastGraphPush[network.ip] >= 60 * 1000) {
// The same mechanic from trimUselessPings is seen here.
// If we dropped the ping, then to avoid destroying the graph, ignore it.
// However if it's been too long since the last successful ping, we'll send it anyways.
if (!lastGraphPush[network.ip] || (timeMs - lastGraphPush[network.ip] >= 60 * 1000 && res) || timeMs - lastGraphPush[network.ip] >= 70 * 1000) {
lastGraphPush[network.ip] = timeMs;
// Don't have too much data!

View File

@ -110,11 +110,6 @@
"ip": "play.gotpvp.com",
"type": "PC"
},
{
"name": "MCLegends",
"ip": "play.mc-legends.com",
"type": "PC"
},
{
"name": "Rewinside",
"ip": "mc.rewinside.tv",

View File

@ -16,9 +16,15 @@ function trimUselessPings(data) {
// 0 is the index of the timestamp.
// See the convertPingsToGraph method.
if (entry[0] - lastTimestamp >= 60 * 1000) {
filteredListing.push(entry);
// This second check tries to smooth out randomly dropped pings.
// By default we only want entries that are online (playerCount > 0).
// This way we'll keep looking forward until we find one that is online.
// However if we can't find one within a reasonable timeframe, select the sucky one.
if (entry[0] - lastTimestamp >= 120 * 1000 || entry[1] > 0) {
filteredListing.push(entry);
lastTimestamp = entry[0];
lastTimestamp = entry[0];
}
}
}