Difference between revisions of "WormNET statistics"

From Worms Knowledge Base

Jump to: navigation, search
(created)
 
(updates)
Line 1: Line 1:
 
{{ParentArticle|[[WormNET (Worms Armageddon)]]}}
 
{{ParentArticle|[[WormNET (Worms Armageddon)]]}}
The [http://stats.worms2d.info/ WormNET statistics] page is a collection of statistical information about WormNET activity. Except for the [[WormNAT2]] graph at the bottom, data is collected by the [[Web Snooper]] bot.
+
The [http://stats.worms2d.info/ WormNET statistics] page is a collection of statistical information about WormNET activity. Data is provided by several sources:
 +
* WormNET activity before February 24, 2009 comes from old [[HostingBuddy]] logs. Since HostingBuddy wasn't very stable and was occasionally put offline for long periods of time, there are gaps in the data.
 +
* WormNET data since February 24, 2009 is provided by [[Web Snooper]] WormNET logs.
 +
* Data for the [[WormNAT2]] traffic graph at the bottom is provided by HostingProxy (the server component of WormNAT2).
  
Activity is measured by '''channel joins''' (thus, a player joining a channel represents one activity measurement unit). This is why W:A users represent the majority in the version distribution chart, even though #AnythingGoes is mostly occupied by snooper users. Up until September 14th 2009, WebSnooper was only present in #AnythingGoes, and thus didn't monitor activity in other channels.
+
WormNET activity is measured by '''channel joins''' (thus, a player joining a channel represents one activity measurement unit). This is why W:A users represent the majority in the version distribution chart, even though #AnythingGoes is mostly occupied by snooper users. For the same reasons, spikes of snooper activity can be observed on days when the bot collecting the logs was restarted several times (since it counts users already present on WormNET every time it connects).
 +
 
 +
Up until September 14th 2009, WebSnooper was only present in #AnythingGoes, and thus didn't monitor activity in other channels. Logging all WormNET channels caused an increase in measured activity, and thus the long-term statistics have been reset to data collected since this date.
  
 
== Timeline ==
 
== Timeline ==
  
 
Here is a list of major events that had an effect on the displayed statistics (whether directly or indirectly).
 
Here is a list of major events that had an effect on the displayed statistics (whether directly or indirectly).
 +
;June 29, 2007
 +
:[[HostingBuddy]] began its sporadic logging of #AnythingGoes activity.
 
;October 13, 2008
 
;October 13, 2008
 
:[[WormNAT2]] server was launched.
 
:[[WormNAT2]] server was launched.
;February 24, 2009
+
;February 24, 2009 (marked by a red line)
:Web Snooper was [http://forum.team17.com/showthread.php?t=38249 released] and began logging #AnythingGoes activity.
+
:Web Snooper was [http://forum.team17.com/showthread.php?t=38249 launched] and began logging #AnythingGoes activity.
 
;June 1, 2009
 
;June 1, 2009
 
:A [[w:memory corruption|memory corruption]] bug that was causing instability in WormNAT2 was fixed, after a day of intensive on-site debugging.
 
:A [[w:memory corruption|memory corruption]] bug that was causing instability in WormNAT2 was fixed, after a day of intensive on-site debugging.
Line 23: Line 30:
 
;August 23-24, 2009
 
;August 23-24, 2009
 
:Another DNS outage that lasted a good part of the weekend. The problem causing random DNS outages is believed to have been fixed on the 25th.
 
:Another DNS outage that lasted a good part of the weekend. The problem causing random DNS outages is believed to have been fixed on the 25th.
;September 14, 2009
+
;September 14, 2009 (marked by a red line)
:[http://forum.team17.com/showthread.php?p=703763#post703763 WebSnooper began logging activity in all WormNET channels]. This caused a spike in accumulated statistics.
+
:[http://forum.team17.com/showthread.php?p=703763#post703763 WebSnooper began logging activity in all WormNET channels].  
 
;September 22-23, 2009
 
;September 22-23, 2009
 
:WormNAT2 server went down for 16 hours due to broken link dependencies.
 
:WormNAT2 server went down for 16 hours due to broken link dependencies.

Revision as of 10:29, 25 September 2009

The WormNET statistics page is a collection of statistical information about WormNET activity. Data is provided by several sources:

  • WormNET activity before February 24, 2009 comes from old HostingBuddy logs. Since HostingBuddy wasn't very stable and was occasionally put offline for long periods of time, there are gaps in the data.
  • WormNET data since February 24, 2009 is provided by Web Snooper WormNET logs.
  • Data for the WormNAT2 traffic graph at the bottom is provided by HostingProxy (the server component of WormNAT2).

WormNET activity is measured by channel joins (thus, a player joining a channel represents one activity measurement unit). This is why W:A users represent the majority in the version distribution chart, even though #AnythingGoes is mostly occupied by snooper users. For the same reasons, spikes of snooper activity can be observed on days when the bot collecting the logs was restarted several times (since it counts users already present on WormNET every time it connects).

Up until September 14th 2009, WebSnooper was only present in #AnythingGoes, and thus didn't monitor activity in other channels. Logging all WormNET channels caused an increase in measured activity, and thus the long-term statistics have been reset to data collected since this date.

Timeline

Here is a list of major events that had an effect on the displayed statistics (whether directly or indirectly).

June 29, 2007
HostingBuddy began its sporadic logging of #AnythingGoes activity.
October 13, 2008
WormNAT2 server was launched.
February 24, 2009 (marked by a red line)
Web Snooper was launched and began logging #AnythingGoes activity.
June 1, 2009
A memory corruption bug that was causing instability in WormNAT2 was fixed, after a day of intensive on-site debugging.
June 19, 2009
WormNET server was inaccessible for a few hours due to migration to another ISP.
July 17, 2009
Team17 DNS servers were down for a few hours.
August 5, 2009
Team17 DNS servers were down for more than a few hours.
August 10-11, 2009
Planned network maintenance.
August 23-24, 2009
Another DNS outage that lasted a good part of the weekend. The problem causing random DNS outages is believed to have been fixed on the 25th.
September 14, 2009 (marked by a red line)
WebSnooper began logging activity in all WormNET channels.
September 22-23, 2009
WormNAT2 server went down for 16 hours due to broken link dependencies.
Personal tools