Big Spikes in egress

maybe time to get 10Gbit :smiley:

I have 280TB and even I dont need 10 GB connection. i have 2x 500/500

1 Like

i duno… my 1Gbit looks pretty pegged at times with the egress.
this isn’t purely Storj, but still the egress is Storj 99% or more

max weekly graph in MB/s

only got 270TB… for some reason i never seem to catch up to you lol

i also host other services, so having the connection pegged isn’t exactly optimal for my other customers.

Did Storj already managed to find out which customer is causing this situation?
If I would be the business owner, I would already sitting with the customer next to a coffee and ask him about the details of his operation. Before it turns out that the Lambos should be sponsored by Storj’s budget…

1 Like

If you overcome limits, you have to pay for it, and limits are not very big.
and as far as we see downloaded speeds, they overcome limits in first minute of spice, so client already pay even for tests.

1 Like

I like egrees, but I am a little worried about my ISP’s infrastructure. I’ve already had problems in the past with large number of concurrent connections triggering ISP router reset, making my node disappear for few minutes, sometimes longer. With my 1000/300 I can saturate it with a few large uploads easily, but thousands of small uploads seem to make a difference here :confused:

Maybe there should be a setting to limit the number of simultaneos connections?

I am sure the Storj team is aware of the larger customer data flows. At the same time, there is nothing unusual here other than some SNO’s are seeing more usage than previously measured in recent months. This kind of activity should be viewed as a kind of Business as Usual/New Normal as we continue to add customers and their usage of Storj increases.

3 Likes

Node name, TB occupied (none full), age:

Node 1 - 6.8TB, 10 months

Node 2 - 11.4TB, 32 months

Node 3 - 9.2TB, 16 months

Node 41 - 6.2TB, 28 months

Node 42 - 4.3TB, 15 months

Node 5 - 8.9TB, 15 months

Node 6 - 5.9TB, 9 months

Node 7 - 9.8TB, 20 months

Node 8 - 7.2TB, 11 months

average size of this nodes?

1 Like

4.5TB-11.5TB. The nodes 41 and 42 are on the same machine, same subnet.

On your screenshots they do not have numbers/names.

You can hold mouse cursor over images and the name will show.

Not all nodes experienced that, its also true on mine 14 nodes.
Those closer to England, DK, and germany was enjoying.
HOWEVER i too saw 100-140GB egress in 1 day.
if every day would look like that, or even HALF OF THAT,
i would soooo shut up, about You know what (prices).

1 Like

Sorry, I know about the lack of info. I did’t have time to fill all the specs. I’ll edit it… The node number is the file name.

1 Like

Again big spike. Still ongoing…

2 Likes

Well now I see the deleted data starting. About as much data went in trash today as I bring in all month. Node growth has been very slow for a while and now it’s basically going backwards at this point.

4 Likes

I don’t expect Storj to take any action about this though until there is a sharp drop off in nodes. Right now they could afford to lose 5k-8k nodes and just not care.

I don’t think we’re going to see to many nodes drop off like that. Most nodes are big players running seed nodes for future expansion. If we do though, it will probably be a lot all at once.

Meh.
Just means I won’t have to start looking for more storage on a couple of my nearly-full nodes :wink:

As I’m not in this for the money I’ll just let the network do its thing.

3 Likes

I went a step further and removed my newest node. After the test sats got removed I ended up with a bunch of free space that just has not been re-filled as yet so the new node just wasn’t needed so I re-deloyed that disk to the NAS.