Huge drop in used data, ~ 7tb out of 22TB across 3 of 6 nodes

[jammerdan]

@pangolin

It seems to be a completely useles number now.

Correct. Instead of telling what you did receive, it is now telling what you may have received.
The only use I see is that you can tell your node is ready to accept uploads.

@pangolin

I wonder why they did this?

@littleskunk

We can’t revert it. We need the performance improvement.

My thoughts on that:

@jammerdan

• Make the databases completely optional unless those which are required. There are node operators who do not care about the statistics and histroy. So everyone who does not care could opt out and provide better performance by doing so.
• I have suggested it many times, still I don’t know if it is fully possible: Move databases to RAM only and make backup to disk in configurable intervals.
• Revert the change, make it configurable if only ordered data is stored because many SNOs have the databases already on SSDs so there is no performance gain from that change.
• Saving bandwidth to a cache (I hope it is RAM cache?) seems fine. If you need more performance increase interval when to flush it to disk. Once ever 10 minutes or even 15 minutes should be sufficient.

Especially when databases are already on SSDs the performance gain is probably negligible.