It’s weird, because this is a drop of like 50% in a week node-wise. But the data stored has not increased much since uploads halted. I guess that doesn’t make much sense replication wise, right?
1 Like
How about the relevant / “responsible for” records per node? Any data on that?
2 Likes
I personally see almost no increase in records stored and/or relevant records in the last 2 days. While node count significantly lowered.
2 Likes
I’m down to 3 nodes now thinking of just shutting them down.
1 Like
Why not let them run? It would look very good if we can reach the next network without losing the current data.
Just let the nodes run, stop thinking about them or look at them.
1 Like
That’s what I plan to do with my 720 nodes.
5 Likes
Good man keep up the good work I’m down to 10 nodes due to bandwidth limitations unfortunately 
1 Like
7 Likes
Thats incredible.
3 Likes
been out the loop travelling for last week and thought there was no chance but i fired up the script and off she went 
i think thats pretty incredible i might even try an upload latter
4 Likes
Very hard to upload new data atm though. Going to have to dust off a test net for dev.
2 Likes
Check jami.net fir testnet chat
When you say full, check the responsible records figures. Once they get up towards 16K records then thats is when to expect data loss
I called them live records to save space in the table header in the screen shot above. So still plenty space for more.
