Guys, this “bug” needs to be fixed, with higher priority. Please.
1 Like
This is not a bug, nothing to fix unfortunately.
Only to implement a new feature for the storagenode:
However, it likely wouldn’t help much, if the node would not receive at least a one report after the gap.
In case ranged loop don’t run tally for one or more days
Not running tally is not a bug, we just need a feature that would hide that bug, oops, that is the non-bug.
However, it’s not a bug, it could be a resources contention though. It will be run eventually and then would send a report. But on the dashboard you will see a gap. The feature should just plot the graph without gaps. This is was an intention for a long time, thankfully to the Community feedback it was changed from fluctuating GBh (which are actual usage in accountable items) to the average usage for the month and more smooth graph.
As far as I know that it doesn’t affect a payout and doesn’t affect payments from customers, it’s only for a pretty reporting.
But I notified the team anyway, the Community always on the top 
This issue may not meet the technical definition of a bug, but it still has a significant impact. It gives the SNO a misleading impression of the node’s status, suggesting that something is wrong when it’s not. This can be demotivating and, more importantly, erodes trust in the data presented by the node, which is a serious concern.
8 Likes
This is a crystal clear bug. No matter what the cause is – resource contention, poor performance or the current moon phase – doesn’t matter. Wrong information present to the user is nothing but a bug.
4 Likes
I passed you opinion to the team. However I can find only one actionable item and it’s classified as a feature.
You may also submit an issue on our GitHub too and you would need to provide examples there why it stop your node from functioning or may be have other impacts, thank you!
Well it keeps declining. We have a waterfall here. Lol. So, now I don’t even know what is the node exact avg disk usage, which is used to calculate the node payout. Why don’t we fix this? Is keeping this bug intentional?
My shape is more even than yours 
1 Like
What is the point of doing stress tests on the nodes, when the satellites cannot function correctly with the current load?
3 Likes
just a visual glitch… not be worried about
3 Likes
I don’t think so. In my opinion there is only 2 numbers that matter. First how much space is used by storj as reported by the OS. Second how much space is paid as reported by the satellite.
Storj is constantly failing to report that second number. How could I trust a business partner who can not tell me at any time how much of my space is paid?
1 Like
I disagree. There is only 1 number that matters. My payout at the end of the month!
3 Likes
The satellite can handle the load. There is maybe the wrong expectation that the satellite has to provide a data point per day. From the satellite point of view that is not nessesary. Summing up the used space every 2 days would still be accurate enough for running the storage node payouts. So no need to panic.
The bigger problem is currently on the storage node side. The satellite could maintain 4 times the current load but the storage nodes are getting problems with used space filewalker, garbage collection and soon TTL deletes. The point of running these kind of tests is to improve on it. Not running these test would mean the customer has to test out the boundaries for us. That is not acceptable!
Edit: Ticket on TTL deletes: Speed up the deletion of expired pieces from nodes · Issue #7053 · storj/storj · GitHub
4 Likes
That number is going down while used space is growing. So you suggesting not to care about the reason?
1 Like
I am questioning the data you are using for this. The graph you see on your dashboard isn’t used for the storage node payout. You can look up the payout data. You can break down the payout data by satellite. That sounds like a better way to find out whats going on with your node.
2 Likes
If you knowing the better way why not implementing it for all SNOs?
It is already implemented. You can look up your payout history and break it down by satellite.
The number I would like to know is how much paid data I am storing today. How to calculate this from payout history?