Back again, this time with overall uptime stats for nodes. Thanks for the suggestion, @weynandkuijpers Need a super reliable node? Look for one of about a hundred that have been powered on for a year or more! Considering the migration to Grid 3 was just over a year ago and required a reboot, I bet we’ll see the number of high endurance nodes increase with time.
Can we get a breakdown of those 93 nodes, I think it would be great to recognize that as an achievement of the farmer. (They definitely aren’t mine , I break my network to much for that)
Was a bit tricky, cause I had to go back and keep track of which network each node is on then sort them accordingly. I probably won’t post this for each week since it’s kinda long, but here’s the breakdown for this week (only 80 nodes remain in the 1 year plus category):
Hi everyone, this is the first stats report since the farmerbot came to mainnet. That means that sleeping nodes are now included in the node count. Actually, it’s probably the case that there were some sleeping nodes on testnet or QA net last week that didn’t get counted (16 on testnet and 0 on QA net are asleep as of today).
I’ll need to update my scripts to include the capacity in the sleeping nodes in the capacity total, so that’s missing for now. Also the utilization percentages won’t count the capacity in sleeping nodes either. Hope to have that all fixed for next week!
New Active Nodes, April 10 – April 17
Total new: 25
Netherlands: 6
United States: 3
Belgium: 1
Slovakia: 3
Vietnam: 6
Germany: 2
United Kingdom: 4
Total Capacity
Online nodes: 2724
Sleeping nodes: 79 Total nodes: 2803 (+44)
Change
Cores
64,654
-0.92%
RAM
420,560 GB
-0.2%
SSD
9,912,784 GB
-0.96%
HDD
33,635,115 GB
-0.99%
Uptimes
Not counting sleeping nodes. Should we include nodes that are asleep but consistently hit their periodic wake up here? Let me know what you think in a reply
Uptime greater than
# of Nodes
% of active nodes
1 Week
2,263
83%
1 Month
1,759
65%
3 Months
1,096
40%
6 Months
605
22%
9 Months
247
9%
1 Year
142
5%
Utilization
Some, but not all standby nodes are included in the capacity totals.
I think we should include nodes that are asleep but consistently hit their periodic wake up because they are part of the grid’s capacity ready and waiting for a workload.
Another quick update before getting into the stats. I realized after posting last week’s numbers that my methodology for classifying sleeping versus online nodes wasn’t quite correct. The quick version is that some nodes were counted twice in the total nodes count but I’m not sure how many. On the flip side, the total capacity figures are actually missing some, but not all of the sleeping nodes, because I didn’t try to add them back in.
The problem turned out to be simpler than I thought. Previously, a node was considered “online” for our purposes here if it had registered an update in the last 24 hours. That might seem a little generous, but it gives a wider view of nodes that are active on the network, even if they’ve been down for a bit (95% uptime, also means up to ~1.5 days downtime per month). Nodes that go to sleep should also report an update about one per day to be considered active, so it turns out these criterion are almost the same.
Since it can take some time for a larger farm to finish waking up all its nodes, the updates for sleeping nodes might be spaced out a bit more than 24 hours. For this time, I just expanded the period to 36 hours for all nodes.
Thanks to @fromenator for chiming in. Just to clarify, all sleeping nodes are included in node counts and total capacity figures. I was just wondering about whether they should be included in the uptime figures, or if we should reserve that for nodes that are actually powered on.
New Active Nodes, April 17 – April 24
Total new: 14
Netherlands: 1
Belgium: 5
Bulgaria: 3
Canada: 2
United States: 2
United Kingdom: 1
Total Capacity
Online nodes: 2609
Sleeping nodes: 121 Total nodes: 2730