Hi All
I’ve been part of Storj since a month, I’ve read a lot about it and I still have some questions that remain unanswered in my head.
I am using 8TB HDD (7.27TB formatted - 10% = about 6.4TB useful) however I’m wondering does HDD performance impact the network. As far as I can understand faster node should receive more traffic than slower one? Am I correct?
I live in Europe, however I am not getting much traffic from Europe. 90%+ of the traffic comes from saltlake and us-central satellites. Is this a miss configuration on my end or just European network does not have that much clients?
In comparison for the last few days I am seeing about 5GB traffic from US servers, while EU servers is about 500MB.
How exactly content delivery works? As far as I understand, when a piece is requested, nodes are competing who will deliver it. Fastest nodes always win, right? I have 300Mbit downstream and 180Mbit upstream network that has 40ms average latency to Europe.
I am using earnings script in Windows PowerShell to check my vetting progress. How can I confirm that I am vetted on any particular satellite?
The closest nodes to the customer will receive more traffic from them.
But it can be far away from others and do not receive traffic from others.
So the answer on your first question - only closeness to the customer makes a difference, not a hardware. In some cases hardware configuration impacts nodes ability to receive traffic - using remote connected drives for example (NFS, SMB, sshfs, iSCSI). They are not supported, only iSCSI can work without issues, but it will be slower than any local connected drive.
The other hardware which can impact your node is using SMR drives.
Any customers’ behavior is normal. There is no average speed for location. Each node behaves individually, because it is used by customers directly.
When the customer wants to download a file, its uplink asks the satellite for 39 random nodes contains their pieces and starts downloads in parallel. As soon as first 29 are downloaded, all remained got canceled. The customer need only 29 pieces from 80 to reconstruct the file. The closest nodes to the customer will win the race.
You can see a vetting progress in percentage in the output of the script (you should not specify a month).
March 2021 (Version: 10.1.0) [snapshot: 2021-03-05 05:14:59Z]
TYPE PRICE DISK BANDWIDTH PAYOUT
Upload Ingress -not paid- 17.71 GB
Upload Repair Ingress -not paid- 4.15 GB
Download Egress $ 20.00 / TB 7.14 GB $ 0.14
Download Repair Egress $ 10.00 / TB 117.36 MB $ 0.00
Download Audit Egress $ 10.00 / TB 186.62 KB $ 0.00
Disk Current Storage -not paid- 677.13 GB
Disk Average Month Storage $ 1.50 / TBm 86.21 GBm $ 0.13
Disk Usage Storage -not paid- 62.07 TBh
________________________________________________________________________________________________________+
Total 86.21 GBm 29.11 GB $ 0.27
Estimated total by end of month 633.52 GBm 213.92 GB $ 2.01
Payout and held amount by satellite:
NODE AGE HELD AMOUNT REPUTATION PAYOUT THIS MONTH
SATELLITE Joined Month Perc Total Disq Susp Down Earned Held Payout
us-central-1 | 2020-11-07 5 | 50% $ 0.53 | 0.00% 0.00% 0.10% | $ 0.0504 $ 0.0252 $ 0.0252
Status: OK
us2 | 2021-01-07 3 | 75% $ 0.00 | 0.00% 0.00% 0.36% | $ 0.0009 $ 0.0006 $ 0.0002
Status: OK
europe-west-1 | 2020-11-07 5 | 50% $ 9.93 | 0.00% 0.00% 0.20% | $ 0.0791 $ 0.0395 $ 0.0395
Status: OK
europe-north-1 | 2020-11-07 5 | 50% $ 4.28 | 0.00% 0.00% 0.00% | $ 0.0149 $ 0.0074 $ 0.0074
Status: 98% Vetted
asia-east-1 | 2020-11-07 5 | 50% $ 0.50 | 0.00% 0.00% 0.11% | $ 0.0341 $ 0.0170 $ 0.0170
Status: OK
saltlake | 2020-11-07 5 | 50% $ 6.14 | 0.00% 0.00% 0.00% | $ 0.0940 $ 0.0470 $ 0.0470
Status: OK
_____________________________________________________________________________________________________________________+
TOTAL $ 21.38 $ 0.2733 $ 0.1369 $ 0.1364
POSTPONED PAYOUT PREVIOUS MONTHS $ 0.5113