lol v1.9.5 improved things a lot :
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100.000%
---------- accepted -----------
Failed: 0
Fail Rate: 0.000%
Canceled: 1
Cancel Rate: 0.096%
Successful: 1039
Success Rate: 99.904%
Confirmed! Just updated 3h ago and successful uploads jumped from 23.4% on v1.6.4 to 99.9%.
Well done Storjteam 
The new success rate numbers posted here are almost at 100%. On average, aren’t nodes expected to loose a certain percentage of races?
I would have expected some lost races due to long tail cancellations. However, we may be looking at the better performing nodes here. People who post right after the update are likely to be better performing nodes. Additionally, transfers may finish so fast that they are done before they can be cancelled. It’s possible more than the success threshold sticks around if that happens.
Once I get the update on my docker node I’ll post my score. Fortunately for this test, I have the opposite of a better performing node. My success rate is currently 9.786%. If my new numbers with the update are above 95% I will be very suspicious. As for transfers finishing to fast, I might be able to do some traffic shaping to test that.
Mine went from 25% to 99.9%. So I wouldn’t be that surprised to see that.
Its still to early to say how good it is give it a few days before all nodes are updated to see real numbers.
I just got the update. It looks like I will need to disable max-concurrent-requests for this new version of the software. I’m getting a lot of:
ERROR piecestore upload rejected, too many requests {"live requests": 101, "requestLimit": 100}.
I would not have thought that a limit of 100 was too small but it seems to keep the requests open for a while and they are adding up over time. The rejections are messing up my “Acceptance Rate” score along with the success rate score.
Quick question here - why do you assume that we may look at the better performing nodes? Don’t necessarily see the connection between people who post after update = have a better rig? 
Ok, so it is possible to get less than 99%.
After installing the update, I let it run until I got at least 1000 successful uploads and here are my numbers:
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 16
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 9
Fail Rate: 3.346%
Canceled: 39
Cancel Rate: 14.498%
Successful: 221
Success Rate: 82.156%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100.000%
---------- accepted -----------
Failed: 0
Fail Rate: 0.000%
Canceled: 98
Cancel Rate: 8.750%
Successful: 1022
Success Rate: 91.250%
========== REPAIR DOWNLOAD ====
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 116
Success Rate: 100.000%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0.000%
Canceled: 133
Cancel Rate: 40.797%
Successful: 193
Success Rate: 59.203%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 1
Success Rate: 100.000%
Info about my node:
Raspberry Pi 4 Model B 2GB
External hard drive with USB 3.0 connection.
Internet connection:60/60
Location: USA East coast.
My rpi 4
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 63
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 3
Fail Rate: 0.676%
Canceled: 16
Cancel Rate: 3.604%
Successful: 425
Success Rate: 95.721%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100.000%
---------- accepted -----------
Failed: 0
Fail Rate: 0.000%
Canceled: 13
Cancel Rate: 0.071%
Successful: 18291
Success Rate: 99.929%
========== REPAIR DOWNLOAD ====
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 789
Success Rate: 100.000%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 4419
Success Rate: 100.000%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 1433
Success Rate: 100.000%
1000/1000 fiber with 10gig backbone. Not sure if really makes much difference though.
my other node crappy speced SMR drive
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 194
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 18
Fail Rate: 0.713%
Canceled: 249
Cancel Rate: 9.869%
Successful: 2256
Success Rate: 89.417%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100.000%
---------- accepted -----------
Failed: 5
Fail Rate: 0.040%
Canceled: 55
Cancel Rate: 0.437%
Successful: 12512
Success Rate: 99.523%
========== REPAIR DOWNLOAD ====
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 2436
Success Rate: 100.000%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0.000%
Canceled: 9
Cancel Rate: 0.253%
Successful: 3543
Success Rate: 99.747%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 746
Success Rate: 100.000%
It wasn’t an assumption, but rather speculation. Enthusiasts tend to have enthusiast hardware. Doesn’t seem so far fetched to me. And it seems that the post right after yours confirmed that it’s not a universal thing to have 99+%.
Ok clear - yeah I get that, even though I would say there are enough raspberry 3 owners (now maybe 4) who just keep it running with an additional disk … Just thinking as my feeling was overall we have more ‘geeks’ in here running a node which could fit that image.
Nevertheless so far it looks pretty good in terms of upload. Once my docker updates I hope it’ll look similar. In my case ‘unfortunately’ I also changed my connection to a better one (hence old successrate improved from 25% to 40% already). Would have been a great test to see how my bad connection plays out here but this one is gone in a week (had both in parallel for a whlie)
not to shabby
only 1hr of log…
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 75
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 0
Fail Rate: 0.000%
Canceled: 4
Cancel Rate: 0.365%
Successful: 1091
Success Rate: 99.635%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100.000%
---------- accepted -----------
Failed: 0
Fail Rate: 0.000%
Canceled: 3
Cancel Rate: 0.275%
Successful: 1086
Success Rate: 99.724%
========== REPAIR DOWNLOAD ====
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 384
Success Rate: 100.000%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 682
Success Rate: 100.000%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 448
Success Rate: 100.000%Yep, just to confirm, both my nodes are RPi 4’s with USB 3.0 connected 5400rpm HDDs (WD Elements). Although, last week I did get a new ISP with 1Gbit fiber up/down, so that might be one reason my successrate numbers pretty high on this new version. Back when I was on V1.6.4, after the ISP upgrade, my successrates were closer to ~10-14% for uploads…with this new version, I’m still rocking >99% upload successrate on both nodes after 8-12 hours.
Node 1:
Node 2:
When I type docker name in the script i get this error :
./successrate.sh: 7: ./successrate.sh: Syntax error: newline unexpected
Also I can’t find the ( storagenode.log ) in the node storage folder, I hope someone can guide me.
I am using KVM remote storage server from some host with ubuntu 18 OS
the successrate.sh script should per default grab the logs from the docker container and process it…
this will however not work, if you have a redirect on your docker storagenode logs to an external location.
if you do have this, then you can add the location of the log you want to process with successrate.sh
./successrate.sh /your/log/location/storagenodewhatever.log
Here you can find the script + additional information
and if you cannot make it work, i’m sure @BrightSilence will want to debug it with you.
my money would be on that it’s a matter of the right location…
link to log redirection, if you done this then you will need to define the log output location when running successrate.sh
Your link had a new line in it.
@msallak1 you shouldn’t edit the script at all. Copying the script might not be a good idea either as sometimes people copy some html mess with it.
Just do
wget https://raw.githubusercontent.com/ReneSmeekes/storj_success_rate/master/successrate.sh
Then call the script with:
./successrate.sh
./successrate.sh containername
./successrate.sh /path/to/node.log
