Rebus and Evmos run together as nodes.
Other networks' power samples: Wind05-Juno(Watts) | Evmos Validator on Wind15 (Watts)
Table 1. Performance of a Rebus + Evmos node (Actual Data, semi-automated feed).
| Timestamp (UTC)16h | RAM usage [GB] Inst | Power [Watt] Inst | ||
|---|---|---|---|---|
| 2022-11-29 14:40:00Z | 16.88 | 49.966 | ||
| 2022-11-30 06:40:00Z | 16.98 | -1 | ||
| 2022-11-30 22:40:00Z | 15.71 | 50.106 | ||
| 2022-12-01 14:50:00Z | 17.34 | 50.76 | ||
| 2022-12-02 06:50:00Z | 17.32 | 52.212 | ||
| 2022-12-02 22:50:00Z | 16.24 | 50.255 | ||
| 2022-12-03 14:50:00Z | 16.41 | 52.482 | ||
| 2022-12-04 07:00:00Z | 16.56 | 49.759 | ||
| 2022-12-04 23:00:00Z | 17.78 | 52.807 | ||
| 2022-12-05 15:00:00Z | 17.18 | 50.538 | ||
| 2022-12-06 07:10:00Z | 17.22 | 52.082 | ||
| 2022-12-06 23:10:00Z | 16.69 | 49.684 | ||
| 2022-12-07 15:10:00Z | 16.9 | 49.948 | ||
| 2022-12-08 07:10:00Z | 18.04 | 52.513 | ||
| 2022-12-08 23:20:00Z | 17.72 | 50.234 | ||
| 2022-12-09 15:20:00Z | 16.91 | 50.622 | ||
| 2022-12-10 07:20:00Z | 16.88 | 50.655 | ||
| 2022-12-10 23:30:00Z | 17.52 | -1 | ||
| 2022-12-11 15:30:00Z | 17.64 | 51.381 | ||
| 2022-12-12 07:30:00Z | 16.28 | 50.257 | ||
| 2022-12-12 23:30:00Z | 17.08 | 50.63 | ||
| 2022-12-13 15:40:00Z | 17.13 | 50.471 | ||
| 2022-12-14 07:40:00Z | 17.7 | 50.078 | ||
| 2022-12-14 23:40:00Z | 17.66 | 50.607 | ||
| 2022-12-15 15:50:00Z | 16.94 | 50.324 | ||
| 2022-12-16 07:50:00Z | 16.84 | 60.382 | ||
| 2022-12-16 23:50:00Z | 18.6 | 50.363 | ||
| 2022-12-17 15:50:00Z | 17.73 | 51.025 | ||
| 2022-12-18 08:00:00Z | 17.44 | -1 | ||
| 2022-12-19 00:00:00Z | 17.01 | 52.246 | ||
| 2022-12-19 16:00:00Z | 17.1 | 50.126 | ||
| 2022-12-20 08:00:00Z | 17.77 | -1 | ||
| 2022-12-21 00:10:00Z | 17.23 | 50.331 | ||
| 2022-12-21 16:10:00Z | 17.78 | -1 | ||
| 2022-12-22 08:10:00Z | 16.93 | 50.476 | ||
| 2022-12-23 00:20:00Z | 15.86 | 49.982 | ||
| 2022-12-23 16:20:00Z | 16.72 | 50.612 | ||
| 2022-12-24 08:20:00Z | 17.02 | 49.766 | ||
| 2022-12-25 00:20:00Z | 3.58 | 63.632 | ||
| 2022-12-25 16:30:00Z | 2.08 | 67.235 | ||
| 2022-12-26 08:30:00Z | 7.09 | 63.049 | ||
| 2022-12-27 00:30:00Z | 1.69 | 66.836 | ||
| 2022-12-27 16:40:00Z | 1.82 | 64.964 | ||
| 2022-12-28 08:40:00Z | 1.81 | 47.368 | ||
| 2022-12-29 00:40:00Z | 1.86 | 47.308 | ||
| 2022-12-29 16:40:00Z | 1.92 | -1 | ||
| 2022-12-30 08:50:00Z | 1.97 | 47.645 | ||
| 2022-12-31 00:50:00Z | 2.05 | 47.447 | ||
| 2022-12-31 16:50:00Z | 2.08 | 47.324 | ||
| 2023-01-01 09:00:00Z | 2.14 | 47.879 | ||
| 2023-01-02 01:00:00Z | 2.16 | 48.775 | ||
| 2023-01-02 17:00:00Z | 2.27 | 47.731 | ||
| 2023-01-03 09:00:00Z | 7.31 | 49.994 | ||
| 2023-01-04 01:10:00Z | 6.13 | 50.804 | ||
| 2023-01-04 17:10:00Z | 14.36 | 50.953 | ||
| 2023-01-05 09:10:00Z | 14.33 | 56.459 | ||
| 2023-01-06 01:20:00Z | 16.4 | 50.554 | ||
| 2023-01-06 17:20:00Z | 13.5 | 53.542 | ||
| 2023-01-07 09:20:00Z | 14.61 | 53.177 | ||
| 2023-01-08 01:20:00Z | 16.14 | 50.091 | ||
| 2023-01-08 17:30:00Z | 14.8 | 49.848 | ||
| 2023-01-09 09:30:00Z | 15.77 | 54.193 | ||
| 2023-01-10 01:30:00Z | 4.0 | 75.055 | ||
| 2023-01-10 17:40:00Z | 3.56 | 68.769 | ||
| 2023-01-11 09:40:00Z | 7.57 | 68.046 | ||
| 2023-01-12 01:40:00Z | 10.34 | 53.927 | ||
| 2023-01-12 17:40:00Z | 14.94 | -1 | ||
| 2023-01-13 09:50:00Z | 17.02 | 51.795 | ||
| 2023-01-14 01:50:00Z | 17.31 | 49.941 | ||
| 2023-01-14 17:50:00Z | 16.88 | 50.115 | ||
| 2023-01-15 10:00:00Z | 16.86 | 50.046 | ||
| 2023-01-16 02:00:00Z | 17.44 | 50.405 | ||
| 2023-01-16 18:00:00Z | 17.43 | 49.994 | ||
| 2023-01-17 10:00:00Z | 18.68 | 56.28 | ||
| 2023-01-18 02:10:00Z | 20.23 | 49.587 | ||
| 2023-01-18 18:10:00Z | 20.06 | -1 | ||
| 2023-01-19 10:10:00Z | 19.6 | 50.032 | ||
| 2023-01-20 02:20:00Z | 21.03 | 60.439 | ||
| 2023-01-20 18:20:00Z | 20.26 | 54.917 | ||
| 2023-01-21 10:20:00Z | 20.06 | 52.951 | ||
| 2023-01-22 02:20:00Z | 19.37 | 50.516 | ||
| 2023-01-22 18:30:00Z | 19.21 | 49.564 | ||
| 2023-01-23 10:30:00Z | 20.99 | 50.01 |
Terms & Concepts
- *Total Bytes Written: The HDD is monitored for write operations in order to learn the MTBF with TBW as the time passing variable.
- ✝: Particular component, serialized by us. Details about each part will follow.
- 16h: 16h aggregates (~10000 Blocks)
- Inst: Instantaneous measurement at timestamp, 1-off.
- ToDo: I/O write errors. This will be helpful to know when we might need to discard the SSD. This should be kept at zero and the general recommendation is not to continue running the SSD in a node where the first IO writing failure occured; therefore this detector will be a good indicator of the end of life of the SSD in order to trigger a replacement.
- Σ : Cumulative sum during the entire life of the applicable component.
- 🔧: Node under planned maintenance. (if any)
- 💥: Unplanned maintenance. (if any)
- ⚡: Power outtage (if any), nodes are covered by an UPS, and now all the fiber routers are also covered by UPS. We would be ready to cover power outtages and/or switch node safely if necessary.
Alternative tools in order to monitor your favourite nodes
- TBD
On slashing parameters
- Medium article on the start stages of the hub, explaining slashing: https://medium.com/node-a-team/understanding-few-key-features-of-cosmos-hub-87394317d10a
Author: @windpowerstake. This work is licensed under a Creative Commons Attribution 4.0 International License..