I must admit I do not see a fair global distribution either.
I had uploaded 2 bigger files: File1 and File2 (Map creation takes a while)
Both show that the distribution of pieces is mainly in the Europe and North America region and I am wondering if this is a desired outcome.
In terms of redundancy and fast worldwide access, I would have expected a broader distribution. Both files seem to have not a single pieces stored in Australia very few in the Asia/Pacific region anyway. Almost none in Africa and very few again in South America.
What is the reaso…
The test files in question have been long deleted. However what I recall is with huge files like 100 GBs or something, the map will have more diverse location display.
The reason?
but this would not make sense in the long run and fraud if you simply pay more for the same.
However what we keep forgetting is:
This confirms what I am trying to figure out here:
So distribution would favor the uploaders location and will distribute the pieces close to his location.
However for redundancy or for collaboration this might not be favorable. A media professional in USA sharing terabytes of data with a production company in Australia might be better off if the data gets close to the location where it is downloaded.
For redundancy it might be better off for a EU customer when his data gets also uploaded f…
Isn’t that something that has been even enforced through the new node selection algorithm that was introduced just a year ago?
I have always wondered about the piece distribution and the usefulness for users:
Because close to the uploader is not always the preferred option for every use case.
I believe ideally uploads should be fast. This means minimum number of uploaded pieces, fast nodes, nearby, longtail cancellation and depending on upload resources either uploading in parallel wit…
Ok. But all this testing and the optimizations have been announced being necessary for customers in the sales pipeline. I believe you have announced that, I can’t remember. So it would be great to learn if with all the tweaking we are gearing towards what those customers expect because at the end this is what everybody wants I guess, to have the network ready to take on the requirements of them. And if there are signs that the progress brings us closer to the deal and the potential customers ar…
And finally the new node selection:
Ok while you are removing any concurrency limit you might have set I will explain how the node selection actually works.
When a segment gets commited to the database it will contain the nodes that have been fast enough and it will be missing the nodes that got long tail canceld. The satellite calculates a success rate for each node with that.
The node selection takes that success rate. Instead of 110 total nodes it selectes 220 nodes at first and compares them in pairs and pick the one with th…
it would not surprise me if satellite keeps sending data to the same fast uploade nodes that the data would end on the very same fast nodes with a limited geographical variety. For a geographically diverse and fair data distribution the upload speed cannot be key.