Just for safety I better post it in this thread as well:
We will do some spot checks regarding the bandwidth our storage nodes have. We will run the new remote benchmark tool against some random selected nodes for a short duration. We are going to use big piece sizes to compensate for the fact that the performance improvements are not rolled out yet. We hope we will still get an accurate reading. The data will be unpaid because we upload the pieces to the storage nodes without commiting the result to the satellite. Garbage collection is going to clean it up later. We will keep the upload burst short to keep the amount of unpaid data as low as possible.
If youād like more nodes to be brought online in specific locations⦠will that be combined with your SLC-capacity-reservation-with-TTL system?
Making an announcement for more nodes somewhere is a relatively weak signal to SNOs⦠but focusing capacity-reservation at existing nodes in your required geo would be a strong one. If you want a extra nodes brought online in a geo: start filling the disks of current nodes with your SLC reservation data
2 of my newest nodes never receive a single vetting attempt from SLC. The rest of the satellites have been fully vetted for months on these nodes. Iām assuming because of this situation (no vetting) they wonāt receive any of this test data. Pls confirm.
Well, in the lat 30 minutes all my nodes have drastically reduced network traffic.
So either Iāve missed it or the tests have been happening and are now completed
You wouldnāt want to read my mind, there is not much thereā¦
I was alluding to my earlier post about severely reduced network traffic and node activity (which you can see by the reduction in all the pretty colours on Disk IO, IOWait, Network, etc.)