Hello again,
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
|
|
Change |
| Cores |
65,820 |
1.8% |
| RAM |
427,622 GB |
1.68% |
| SSD |
9,933,341 GB |
0.21% |
| HDD |
33,327,683 GB |
-0.91% |
Uptimes
| Uptime greater than |
# of Nodes |
% of active nodes |
| 1 Week |
2,260 |
83% |
| 1 Month |
1,666 |
61% |
| 3 Months |
1,056 |
39% |
| 6 Months |
605 |
22% |
| 9 Months |
319 |
12% |
| 1 Year |
148 |
5% |
Utilization
Mainnet Utilization
|
|
|
| Cores |
1,928 / 64,509 |
(2.99%) |
| RAM |
2,587 / 418,196 GB |
(0.62%) |
| SSD |
46,303 / 9,859,600 GB |
(0.47%) |
| HDD |
1,074 / 33,031,753 GB |
(0.0%) |
Testnet Utilization
|
|
|
| Cores |
105 / 1,311 |
(8.01%) |
| RAM |
309 / 9,426 GB |
(3.27%) |
| SSD |
3,551 / 73,741 GB |
(4.82%) |
| HDD |
172 / 295,930 GB |
(0.06%) |
Total Utilization
|
|
|
| Cores |
2,033 / 65,820 |
(3.09%) |
| RAM |
2,896 / 427,622 GB |
(0.68%) |
| SSD |
49,854 / 9,933,341 GB |
(0.5%) |
| HDD |
1,246 / 33,327,683 GB |
(0.0%) |
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.
, I break my network to much for that)