Successrate.sh comparison thread

Hey SNOs :slight_smile:

I know there are lot’s of threads where we talk about successrate.sh results and hardware but it’s comes up when issues are there - I would love to share outputs for comparison, not for hardware geeking…

How do you feel about this format:
Hardware: Synology DS1019+ (INTEL Celeron J3455, 1.5GHz, 8GB RAM) with 20.9 TB in total SHR Raid
Bandwidth: Home ADSL with 40mbit/s down and 16mbit/s up
Location: Amsterdam
Node Version: v0.21.3
max-concurrent-requests: DEFAULT, so 7
successrate.sh:

========== AUDIT =============
Successful: 2107
Recoverable failed: 0
Unrecoverable failed: 0
Success Rate Min: 100.000%
Success Rate Max: 100.000%
========== DOWNLOAD ==========
Successful: 36008
Failed: 3828
Success Rate: 90.391%
========== UPLOAD ============
Successful: 8835
Rejected: 4
Failed: 1490
Acceptance Rate: 99.955%
Success Rate: 85.569%
========== REPAIR DOWNLOAD ===
Successful: 0
Failed: 0
Success Rate: 0.000%
========== REPAIR UPLOAD =====
Successful: 0
Failed: 0
Success Rate: 0.000%

My biggest issue is my bandwidth, hardware is now fine but with home ADSL Router I don’t think more “max-concurrent-requests” etc. will help :slight_smile:
Success Rates so far are ok for me, but not sure what other are.

1 Like

I’m fairly new to Storj, so my information may be a little bit incorrect…

However, after paging through the logs and some of the documentation/forum posts, it seems that the “success” rates have the following practical meaning:

  1. Audits:
    These are sent to a particular node as a test. Under normal operations, this should be 100%. And if the number falls below 60%, your node will likely be disqualified on the network.

  2. Download and Upload percentages:
    These are at least partially related to:

    1. Your geographical distance from a satellite.
    2. The speed at which your node processes requests.

If your node is too slow in comparison with other nodes in the same geo-ip and/or subnet than your node will lose the race to get the data in or our first. When your node loses the race, the “success” rate declines.

In my case, I’m not close to a satellite node and I’m tunneling traffic through a secure pipe in order to avoid being blocked by my ISP. So, there’s a little bit extra overhead in my IP traffic… However, I’m also the only node in my /24 IP block.

So, the success rates parsed from the node log don’t tell the complete story of your node. Judging by my own rates of Upload and Download, your node is doing quite well. It is beating out the competing nodes most of the time.

Also… the log parsing script is not very efficient… it works, but there’s definitely room for improvement. Multiple grep statements per line creates significant a bottleneck. However, it’s all volunteer… and my own shell programming is bit utilitarian as well. I was thinking of taking some time this week to look at some improvements and posting them. But I see other activity in making the web interface much more informative.

Please correct my errors in reasoning if I’ve got the “success” rate information incorrect.

Thanks for your reply. I’m fairly clear on what what means, but thanks for the explanation from your side. Main concept of this thread was to just compare output between SNOs just to get a feeling where others are netting out.
:+1:

Hardware : Crappy HP laptop (AMD E1-2100, 1.0Ghz, 4Gb RAM), 1 TB hdd on usb 3.0 dock
Bandwidth : Home optical fiber 100 mbit/s up and down
Location : Oulu, Finland
Node Version : v0.21.3
max-concurrent-requests : 10
successrate.sh :

========== AUDIT =============
Successful: 3183
Recoverable failed: 0
Unrecoverable failed: 0
Success Rate Min: 100.000%
Success Rate Max: 100.000%
========== DOWNLOAD ==========
Successful: 100518
Failed: 25000
Success Rate: 80.082%
========== UPLOAD ============
Successful: 32321
Rejected: 36
Failed: 2965
Acceptance Rate: 99.889%
Success Rate: 91.597%
========== REPAIR DOWNLOAD ===
Successful: 0
Failed: 0
Success Rate: 0.000%
========== REPAIR UPLOAD =====
Successful: 0
Failed: 0
Success Rate: 0.000%

1 Like

Update:

Hardware : Synology DS1019+ (INTEL Celeron J3455, 1.5GHz, 8GB RAM) with 20.9 TB in total SHR Raid
Bandwidth : Home ADSL with 40mbit/s down and 16mbit/s up
Location : Amsterdam
Node Version : v0.22.1
max-concurrent-requests : DEFAULT, so 7
successrate.sh :

========== AUDIT ============= 
Successful:           1036 
Recoverable failed:   0 
Unrecoverable failed: 0 
Success Rate Min:     100.000%
Success Rate Max:     100.000%
========== DOWNLOAD ========== 
Successful:           17783 
Failed:               1942 
Success Rate:         90.155%
========== UPLOAD ============ 
Successful:           2972 
Rejected:             2 
Failed:               752 
Acceptance Rate:      99.933%
Success Rate:         79.807%
========== REPAIR DOWNLOAD === 
Successful:           1 
Failed:               0 
Success Rate:         100.000%
========== REPAIR UPLOAD ===== 
Successful:           36 
Failed:               0 
Success Rate:         100.000%

For the first time in a while got an REPAIR DOWNLOAD and some REPAIR UPLOAD.
No change vs. before just my UPLOAD Success Rate went a bit down which is IMO normal because of my ‘small’ connection. So far only 2 rejected which means concurrent rate for now ok.

FYI

Well, let’s go:
Hardware : Supermicro server, 2x Intel Xeon X5687, 100GB RAM. 6x4TB hard drives in raidz2 with two SSDs for L2ARC and ZIL. The node runs inside a VM with 32GB RAM. The node is not the only VM there.
Bandwidth : Home GPON with 1gbps down and 600mbps up. Backup connection is DOCSIS with 100mbps down and 12mbps up
Location : Lithuania
Node Version : v0.22.1
max-concurrent-requests : 64

results from the last 75 hours since the update:

========== AUDIT =============
Successful:           4270
Recoverable failed:   4
Unrecoverable failed: 0
Success Rate Min:     99.906%
Success Rate Max:     100.000%
========== DOWNLOAD ==========
Successful:           25538
Failed:               1283
Success Rate:         95.216%
========== UPLOAD ============
Successful:           3262
Failed:               238
Rejected:             0
Acceptance Rate:      100.000%
Success Rate:         93.200%
========== REPAIR DOWNLOAD ===
Successful:           129
Failed:               2
Success Rate:         98.473%
========== REPAIR UPLOAD =====
Successful:           30
Failed:               0
Success Rate:         100.000%

Concurrent requests do not go very high, they stay below 6 right now. Used to be more during the stress tests.

Update, 40 hours of v0.23.3
Hardware : Synology DS1019+ (INTEL Celeron J3455, 1.5GHz, 8GB RAM) with 20.9 TB in total SHR Raid
Bandwidth : Home ADSL with 40mbit/s down and 16mbit/s up
Location : Amsterdam
Node Version : v0.23.3
max-concurrent-requests : DEFAULT, so 7
successrate.sh :

========== AUDIT ============= 
Successful:           1136 
Recoverable failed:   0 
Unrecoverable failed: 0 
Success Rate Min:     100.000%
Success Rate Max:     100.000%
========== DOWNLOAD ========== 
Successful:           10269 
Failed:               799 
Success Rate:         92.781%
========== UPLOAD ============ 
Successful:           2611 
Rejected:             8 
Failed:               321 
Acceptance Rate:      99.694%
Success Rate:         89.052%
========== REPAIR DOWNLOAD === 
Successful:           0 
Failed:               0 
Success Rate:         0.000%
========== REPAIR UPLOAD ===== 
Successful:           3 
Failed:               0 
Success Rate:         100.000%