Income on each production satellite

Node Operators
1

According to my personal stats, for nodes in EU, the income on 2 nodes in different locations look like this:

Old node - gross income in 46 months:
AP1 - 48.6$ (~7.5%)
US1 - 379$ (~58.5%)
EU1 - 221$ (~34%)

Young node - gross income in 8 months:
AP1 - 0.4$ (~1%)
US1 - 34.3$ (~79.5%)
EU1 - 8.5$ (~19.5%)

ap1 has lost activity in 4 years, dropping to an insignificant 1%.
eu1 has lost some activity, but us1 gained activity and is the biggest market.
“lost” and “gained” activity are not the right words, but you get what I mean.
So we should focus in gaining more clients in Europe and Asia.

Something strange… On the same machine with 2 nodes sharing the same IP, one is 8 months, the other 7 months. The younger one made 7$ on EU1 and the older one made only 1.5$ on EU1, as gross income. How can this be?

2

Each location and node are unique, the customers are not predictable, the usage almost random.
Why should different nodes behave the same way?

3

The nodes at the bottom (not the ones in the table) are both on the same machine, sharing the same IP. The hardware and settings are the same, the internet connection is the same.
The younger one made more on a satellite than the older one. Shouldn’t be the other way around?
Ahh, writing this now I just remembered the test on SL and the bug about used space. I believe the older one got “full” before the younger one, and stopped the ingress.

4

They still have different NodeID, thus stores data of different segments, likely from different customers.
There is also a choice of n rule, maybe the oldest has a little bit worse success rate.

That’s quitely possible.

5

does anything like the AWS S3 gateways (or whatever they are called) work only through the US1 satellite?

6

They are working independently of the satellite. Just reminder - the satellite is an address book, the metadata database, auditors and repairers, also payments processor. However, it doesn’t used as a proxy for the customers data.
The S3 gateway is a different beast. It is a middleman between nodes and the customers, because it translates the S3 requests to the Storj native requests, thus it passes data through it. However, these gateways are distributed services as nodes. Yes, the number is less than 20k yet, but they are distributed over the world as everything in Storj (including satellites and their databases).

P.S. Honestly, I still wonder why we still split them up? It seems to me that we just need to run one, it will be distributed around the world anyway, so you will always be connected to the closest instance. So, having three metadata sources sounds like three separate networks.
Only to test how the Community Network would look like? In that case it makes sense.

1 Like