I agree egress revenue is of paramount importance, BUT only if it is not being withheld. In theory, (the opportunity for) egress maximizes when data stored is maximized. The 5 TB statistic is good feedback as I was wondering about that too. Allowing for the recommended 10% overhead, my server will max at 9 TB across the 5 HDD nodes. It’s a dual server, so I could do the same on the other side (but with Windows) By that time, it would be nice if the stars align and both are earning enough to make investing in a purpose built rig worthwhile. That’s when my node might finally be bigger than yours .
That seems to be a number from experience of multiple people. My nodes hold 4.5TB at the moment and I’m operating them since June (there were some network wipes since then) and I’m close to the main testing satellite.
Ahh you were talking about escrow. Now I get what you were going for. Yes when you start them one by one, some nodes will have escrow held back for longer. But despite that, the much more traffic and data you’ll be able to get by that method will far outperform the escrow held back. Especially if you consider that half the held back amount is returned to you after 15 months.
As for that 5TB number, @kevink is exactly right. I have a good node in a good location and I know mine is only slightly below the largest ones. I’m currently storing 4.2TB. So it’s highly likely that if you have 3 of your nodes up and running, you will have maximized your performance for a while to come already. I can imagine wanting all 5 up and running just to be ready for more data, but I don’t really expect that to fill up. Especially since I assume a lot of test data will be gradually removed from nodes as customers start using it more as well.
Showing a “largest node” statistic in the SNO board would be helpful information. It might also serve as a check against over-compensating within the community.
Suggestions about sharing more network stats have been around for a while. Best is to post these ideas on ideas.storj.io or upvute the ones already there. I agree that some people seem to want to go overboard and these numbers help them determine that’s probably not the best idea.
So, I’m back at it with this Node2 thing, but I am having problems with authorization for the 2nd token. I think it may have something to do with the revocations.db and my folder structure.