From what I can tell everyone saw a drop. It’s likely optimizations that cause transfers to finish faster which increases the logging issue. From what I can tell there is no actual drop. Don’t waste too much time on red herrings.
yeah ill try lol… i always thought it might be the other way around… the log being instantly updated when the command came in from the satellite while there would be a delay on the completion of the uploaded file.
but i suppose if there was optimizations done and that was the case, then we should have seen an increase in successrates.
If the optimizations were done on the uplink side, it could be finishing earlier and closing the connection earlier. Leading to the node logging a canceled line after it’s done with its work. That’s just speculation though.
1 Like
After seeing test traffic return today (happy to see that!) I decided to check out my numbers and do some more sample testing.
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 171
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 1
Fail Rate: 0.083%
Canceled: 7
Cancel Rate: 0.583%
Successful: 1193
Success Rate: 99.334%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100.000%
---------- accepted -----------
Failed: 0
Fail Rate: 0.000%
Canceled: 3698
Cancel Rate: 74.647%
Successful: 1256
Success Rate: 25.353%
========== REPAIR DOWNLOAD ====
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 652
Success Rate: 100.000%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0.000%
Canceled: 192
Cancel Rate: 75.889%
Successful: 61
Success Rate: 24.111%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 179
Success Rate: 100.000%
It’s save to say numbers on my node have never looked this bad. I used to have upload success in the 80-90% range, which dropped to 60% a while ago and now shows between 25 and 30%. However, after doing several more sample tests. Didn’t count them this time, but I think I did around 10. All of the pieces that showed up as upload cancelled actually ended up on my HDD anyway. I think we can now safely conclude that these success rate numbers are meaningless until the logging issue is fixed.
2 Likes
As of right now, my node is still sitting at about 75% upload as well as upload-repair success rates from June 1st running V1.5.2
After the giant data deletion last month, I’m almost back to full again… 4.77 GB left.
If I understand little skunk correctly, it’s normal for cancelled uploads to stay on the hard drive for a while. Garbage collection sorts them out later.
I suspect this is where much of my nodes trash is coming from, cancelled uploads that were eventually deleted by the garbage collector. I recently increased my storage by about 33GB(on my full node), and a few days later, after it was full again, the amount of trash on my node went from a few hundred MB, to about 9GB. I’m guessing that means that about 9GB of the 33GB received was cancelled which means my node kept 72% of it(72% successrate?). But that’s just guessing/assuming/hoping on my part. The successrate.sh script says my success rate is 10%. Ouch.
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 13198
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 5335
Fail Rate: 3.389%
Canceled: 7455
Cancel Rate: 4.736%
Successful: 144608
Success Rate: 91.874%
========== UPLOAD =============
Rejected: 39828
Acceptance Rate: 87.555%
---------- accepted -----------
Failed: 1337
Fail Rate: 0.477%
Canceled: 250282
Cancel Rate: 89.321%
Successful: 28586
Success Rate: 10.202%
========== REPAIR DOWNLOAD ====
Failed: 267
Fail Rate: 0.585%
Canceled: 1
Cancel Rate: 0.002%
Successful: 45361
Success Rate: 99.413%
========== REPAIR UPLOAD ======
Failed: 87
Fail Rate: 0.134%
Canceled: 60370
Cancel Rate: 92.850%
Successful: 4562
Success Rate: 7.016%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 96981
Success Rate: 100.000%
@Mark
so high numbers of deleted files on a regular basis might means lots of lost races / cancelled uploads… ofc does 1/8th a piece even count as a deletion… i mean ARRRR we not pirates…
thats interesting…
@anon27637763
i suppose some people might not be affected for various reasons… if you are running different OS, or what type of cpu / system you are running… i bet one of those old SPARC cpu’s would be great at stuff like this.
personally i’m not to fond about my cpu only running on 2.13ghz because if your clock is running slow there is a longer response time on most things…
my successrates are lovely tho… 53% upload… lol
partly because i am trying to migrate my node to a 512n pool rather than mixed 4k, 512n, sas,sata drives… not sure it will help much… but maybe it will make everything run better…
sure is taking a long time to copy my node this time… only 8.5tb and so far 5.3 tb done in maybe 3 days…or 4 days but did have 1 full day that was mostly a scrub which stalled the copy
done like 2.1 mil files in the last two days…i just think it was faster last time… ofc that was a copy on the same pool… this is to another pool on other drives… so should really be faster…
Right, I should jot down a few of those piece ID’s and check in a few days if they stick around. I don’t expect a large amount of them will be deleted though. My trash folder isn’t that big. I currently have 1.49GB trash on a 12TB node. So that suggests only a fraction gets trashed. But I’ll check again later.
1 Like
might be interesting to be able to track that over say a month or forever and be able to compare numbers with say nodes which get like 13% which is the lowest i’ve seen somebody have.
So I concluded that my low percentage was due to the fact that I was cryptomining using CPU on the same computer (although using only 3 cores out of 4, i.e. 3 threads out of 8).
By stopping the CPU mining, I was able to raise upload success rate to over 40% in 3 days as well as repair to over 40%.
To give a better idea for the node:
CPU: Intel Core i7-4700HQ 4x2.4 GHz (4core/8thread), boost up to 3.4 GHz
RAM: 2x8 GB DDR3 1866 MHz
System drive: Kingston SSD 240 GB SATA3
Node drive: Seagate Constellation ES.2 3 TB HDD
OS: Ubuntu 20.04 LTS
Network download/upload: fiber-optic 1Gbps/600Mbps
Also, the traffic has started coming in since yesterday even more than in May:
And the successrate:
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0,000%
Recoverable failed: 2
Recoverable Fail Rate: 0,551%
Successful: 361
Success Rate: 99,449%
========== DOWNLOAD ===========
Failed: 14
Fail Rate: 0,276%
Canceled: 5
Cancel Rate: 0,099%
Successful: 5052
Success Rate: 99,625%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100,000%
---------- accepted -----------
Failed: 0
Fail Rate: 0,000%
Canceled: 35134
Cancel Rate: 47,822%
Successful: 38335
Success Rate: 52,178%
========== REPAIR DOWNLOAD ====
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 0
Success Rate: 0.000%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0,000%
Canceled: 3377
Cancel Rate: 57,500%
Successful: 2496
Success Rate: 42,500%
========== DELETE =============
Failed: 0
Fail Rate: 0,000%
Successful: 1703
Success Rate: 100,000%
1 Like
I’m asked to post a successrate for my rpi3 b+, 2TB. It is not makes any sense, because the node is full. But if you want to know, here is it:
======== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 11747
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 458
Fail Rate: 0.470%
Canceled: 732
Cancel Rate: 0.752%
Successful: 96158
Success Rate: 98.778%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 0.000%
---------- accepted -----------
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 0
Success Rate: 0.000%
========== REPAIR DOWNLOAD ====
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 53158
Success Rate: 100.000%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 0
Success Rate: 0.000%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 2668
Success Rate: 100.000%
1 Like
Hello, how do get this screen ?
Links after the first topic
1 Like
I haven’t checked specific pieces, but I kept an eye on the trash folder. While it grew a little, it’s never been bigger than 2.5GB. So clearly the vast majority of canceled uploads are actually sticking around. So while this script still says I have less than 30% successful, in reality it seems to be more than 90%.
I have 40GB trash v. 830GB data. Looks like a lot of stuff got deleted in the last few days.
Trash isn’t used for normal delete operations. It’s used for when data is on your node that shouldn’t be there. This can happen because your node was offline during delete operations or because the operation timed out previously. It can also happen because the cancelled transfers left pieces behind that really shouldn’t be on your node. I can’t tell you where your trash came from. But I can say that on a node that didn’t used to have a low successrate, like mine, these canceled transfers don’t appear to generate big amounts of trash.
Thanks for that. I take it that it will sort itself out.
Hi. Here is my success rate: (log since May 27th, 20)
Node 1 on Pi 4
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 12222
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 2121
Fail Rate: 1.729%
Canceled: 3097
Cancel Rate: 2.524%
Successful: 117481
Success Rate: 95.747%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100.000%
---------- accepted -----------
Failed: 28
Fail Rate: 0.004%
Canceled: 599747
Cancel Rate: 85.436%
Successful: 102209
Success Rate: 14.560%
========== REPAIR DOWNLOAD ====
Failed: 1
Fail Rate: 0.005%
Canceled: 0
Cancel Rate: 0.000%
Successful: 19908
Success Rate: 99.995%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0.000%
Canceled: 63780
Cancel Rate: 88.100%
Successful: 8615
Success Rate: 11.900%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 151518
Success Rate: 100.000%
Node 2 on other Pi4 (same network)
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 5475
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 950
Fail Rate: 1.827%
Canceled: 1238
Cancel Rate: 2.380%
Successful: 49823
Success Rate: 95.793%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100.000%
---------- accepted -----------
Failed: 34
Fail Rate: 0.005%
Canceled: 610183
Cancel Rate: 85.688%
Successful: 101878
Success Rate: 14.307%
========== REPAIR DOWNLOAD ====
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 328
Success Rate: 100.000%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0.000%
Canceled: 57380
Cancel Rate: 88.363%
Successful: 7557
Success Rate: 11.637%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 150495
Success Rate: 100.000%
Node 3 in data center
========== AUDIT ==============
Critically failed: 0
Critical Fail Rate: 0.000%
Recoverable failed: 0
Recoverable Fail Rate: 0.000%
Successful: 1310
Success Rate: 100.000%
========== DOWNLOAD ===========
Failed: 188
Fail Rate: 1.707%
Canceled: 263
Cancel Rate: 2.387%
Successful: 10565
Success Rate: 95.906%
========== UPLOAD =============
Rejected: 0
Acceptance Rate: 100.000%
---------- accepted -----------
Failed: 10
Fail Rate: 0.004%
Canceled: 76224
Cancel Rate: 32.503%
Successful: 158277
Success Rate: 67.492%
========== REPAIR DOWNLOAD ====
Failed: 0
Fail Rate: 0.000%
Canceled: 0
Cancel Rate: 0.000%
Successful: 1011
Success Rate: 100.000%
========== REPAIR UPLOAD ======
Failed: 0
Fail Rate: 0.000%
Canceled: 8619
Cancel Rate: 32.579%
Successful: 17837
Success Rate: 67.421%
========== DELETE =============
Failed: 0
Fail Rate: 0.000%
Successful: 68458
Success Rate: 100.000%
How you use succesrate.sh? I follow the instrucctions but all the stats is 0%… Im doing something wrong
Please post the command you are using.