Hello Storj Community, We are excited to announce some changes that we have begun to implement regarding how we are using test data on the network! What is changing We are currently seeing exponential growth in our paid customer data and expect that trend to continue based on our sales pipeline. …

Yeah, that was clearly a joke. You quoted it by skipping the first part of the sentence and omitting the emoji, both of which made it pretty clear that was not a serious suggestion.

Isn’t it in fact “crap” for the lower 50% of nodes? :thinking:

It seems that it will be more percentile-ish. The fastest node out of the bunch will be selected 100% of the time, a median node will be selected 50% of the time, etc.

[image] littleskunk: I am on the technical side and don’t feel comfortable talking about sales. 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 …

[image] IsThisOn: That node could win races with a fast node and never will be able deliver his data fast. Interesting times ahead! :smiling_face_with_three_hearts: Oh yes that is an interesting thought. We have these silly limited lines here all over. And even fibre is being sold not as s…

[image] IsThisOn: 1Gbit download and 50mbit Upload. That node could win races with a fast node and never will be able deliver his data fast. Interesting times ahead! I might have misinterpreted your initial question. I assumed you meant whether downloads are also selected using power of 2 n…

I’m sure a lot of people are waiting for this: did we actually manage to hit the goals with last night’s test? How far off are we if we didn’t?

I’m still seeing a lot of ingress on my nodes, I wonder if the test is still ongoing…

Been sitting at ~25% Trash for several days now. Is this the new normal? [image]

Storj Community Forum (official)

Updates on Test Data

Announcements

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled