Bandwidth utilization comparison thread

Maybe Mighty Greek showed his might ! he spun a node and everyone got the increase in traffic :rofl:

Sorry :slight_smile:
Stored is in TB, other numbers are ratios.

usage:   0.20381 

means that on average egress usage on this node was 20.38% of data it has stored, per day

usageM:  6.11430

is the previous number multiplied by 30 to estimate total usage per month
repair numbers are similar, they represent repair upload.

there is no such rule… and I got 130GB ingress yesterday.
Also as you know I have 3 nodes and never did I encounter an increase of ingress. It’s technically impossible! The satellite has a list of nodes that are selected for upload and if your node goes offline, it’ll stay in that list for 4 hours. But if a new node comes online, it’ll be added to that list immediately (otherwise it would not receive data) and therefore the traffic gets split. It’s impossible that you suddenly get more ingress.

1 Like

yeah, first day is waaaay above average on my node too. But it quickly goes down as more data is collected.

I think what he means by rule it the fact that since the start of this thread no one reported an ingress of more than 130GB but again everyone seems to have had an increase in ingress yesterday.

thats funny because thats what the data has been saying for the last 14 days…

there was a max daily ingress which all nodes without limitation or issues would run into…
ofc it’s not a max in the sense of it being a set quantity, but as in nobody would be faster than that… even if they had multiple nodes, singular nodes, or super internet… all of the nodes would reach the exact same peak within 1% or a few % each day…

the data is pretty clear about that…

 July 3rd
    dragonhogan - ingress 17.75 - egress 19,58 = 1,89 ‰ of stored 10,31 TB
    Mark        - ingress 18.17 - egress 3,14  = unknown
    SGC         - ingress 17.40 - egress 19,34 =  1,77 ‰ of stored 10,9 TB 
    striker43    - ingress 25,2 - egress 36,93 =  3,62 ‰ of stored 10,2 TB
    (had to extrapolate here so striker numbers are highly inaccurate)

4th July
Mark        - ingress 57,97 - egress 3,14  = ‰ of stored
SGC         - ingress 55,32 - egress 23,58 = 2,16 ‰ of stored 10,9 TB - (still with stability issues)
kevink      - ingress 48.05 - egress 9,73   = 2.86 ‰ of stored - 3,4 TB approx
(seems slightly off, but have been changing/tinker numbers of nodes)

striker43   - ingress 57,75 (i will assume mark and striker are the two accurate numbers here)
dragonhogan - ingress 57,03 - egress 22,63 = 2,20 ‰ of stored 10,31 TB approx

July 5th
striker43       - ingress 105,81
SGC             - ingress 104,20 - egress 32,39 = 2,97 ‰ of stored 10,9 TB 
Kevink          - ingress 106,07 - egress 17,61 = 5,18 ‰ of stored 3,4 TB approx
Krystof         - ingress 106,15 - egress 38,24 = 3,55 ‰ of stored 11,85 TB
dragonhogan     - ingress 101,62 - egress 34,74 = 3,37 ‰ of stored 10,31 TB approx
the mighty geek - ingress 105,45 - egress 6,27  = 5,22 ‰ of stored 1,2 TB

6th july
striker43       - ingress 112,83 - (missing egress)
dragonhogan     - ingress 108,38 - egress 34,33 = 3,32 ‰ of stored 10,31 TB
TheMightyGeek   - ingress 113,09 - egress 6,87  = 5,72 ‰ of stored 1,2
SCG             - ingress 108,71 - egress 32,64 = 2,93 ‰ of stored 11,11TB
zagg            - ingress 108,77 - egress 6,52  = 4,93 ‰ of stored 1,32 TB

7th july
TheMightyGeek - ingress 109,30 - egress 6,06  = 5.0 ‰ of stored - 1,3 TB
SGC           - ingress 109,96 - egress 29,61 = 2.6 ‰ of stored - 11,21 TB
kevink        - ingress 109,60 - egress 15,69 = 4.6 ‰ of stored - 3.4 TB approx
dragonhogan   - ingress 104,21 - egress 29,11 = 2,8 ‰ of stored - 10,31TB
striker43     - ingress 109,76 - egress 25,58 = 2.5 ‰ of stored - 10,2TB

July 8th
TheMightyGeek - ingress 113,82 - egress 7,13  = 5.50 ‰ of stored 1,4 TB
SGC           - ingress 114,14 - egress 36,49 = 3.20 ‰ of stored 11,33 TB
Dragonhogan   - ingress 108,71 - egress 41,79 = 4,03 ‰ of stored 10,35 TB
striker43     - ingress 114,25 - egress 36,31 = 3,52 ‰ of stored 10,31 TB 

9 July
Dragonhogan   - ingress 98,57  - egress 67,20 =  6,41 ‰ of stored 10,48 TB 
SGC           - ingress 103,8  - egress 42,75 =  3.75 ‰ of stored 11,39 TB
TheMightyGeek - ingress 102,65 - egress 7,13  =  6,89 ‰ of stored  1,49 TB
 kevink       - ingress 102,73 - egress 45,78 = 12,71 ‰ of stored  3,60 TB
(exceeded 1% congratz - i kinda feel a bit left out egress wise lol)

JoshGarza - data inconclusive


10 july 
Dragonhogan   - ingress 107,53 - egress 67,20  = 6,75 ‰ of stored 10,47 TB
TheMightyGeek - ingress 105,78 - egress  7,13  = 6,81 ‰ of stored  1,6 TB
kevink        - ingress 109,26 - egress 47,75 = 12,76 ‰ of stored 3,74 TB
SGC            - ingress 109,89 - egress 47,02 = 4,07 ‰ of stored 11,54 TB

11 July 
SGC           - ingress 118,39 - egress 59,78   = 5,13 ‰ of stored 11,64 TB
TheMightyGeek - ingress 117,14 - egress 11,09   = 6,41 ‰ of stored  1,73 TB
kevink        - ingress 117,66 - egress 44,19   = 11,5 ‰ of stored 3,84 TB
dragonhogan   - ingress 115,75 - egress 73,64   = 6,97 ‰ of stored 10,56 TB

12 july 
SGC           - ingress 114,58 - egress 71,56  = 6,09 ‰ of stored 11,75 TB
TheMightyGeek - ingress 113,97 - egress  11,2  = 6,15 ‰ of stored 1,82 TB
kevink        - ingress 113,68 - egress 37,18  = 9,40 ‰ of stored 3,95 TB
dragonhogan   - ingress 111,00 - egress 68,49  = 6,41 ‰ of stored 10,68 TB

I guess they started a new project/test on europe-north and uploaded more data, we’ll see if it keeps going like this or if it settles back down.

anyone else get this spike today…
image

@TheMightyGreek
see why one cannot use that graph for much…
from 250 to 375 in a day and then tomorrow it will most likely do a deep dive…
it’s numbers are so unreliable it’s ridiculous…

I actually had a slight dip compared to the day before yesterday even with the 120GB of ingress…

Yep, I saw it too. Looking at the “All Satellite” Graph and then drilling down to the individual satellite graphs, it appears that it’s the Saltlake satellite that has the most variation from day to day, and specifically had the big spike up yesterday. That satellite has always had some issues with reporting consistent space used data on a day-to-day basis.

1 Like

ah right… maybe it’s overloaded again…

last time it was like months behind with some of the data… i suppose that might be related…

interesting that more people see the spike tho…

@TheMightyGreek
it’s not ingress its data stored…
the graph claims i had an additional 5tb additional disk space used yesterday…

yes my phrasing wasn’t very clear

My graphs look very much like yours, saltlake all over the place and europe north goes up and down but nothing extreme.

1 Like

well haven’t really looked at it to much… was keeping an eye on it in the beginning… but then i noticed how all over the place it was and then i just sort of ignored it until now…

but i suppose it might just be the stress on some of the satellites that is doing it…

anyways just wanted to prove my point about why it’s almost a useless graph currently, now that there was the chance… and why it shouldn’t be used for anything… atleast until it works correctly…

and i got curious to know, if it was a local or a network thing…

1 Like

This is correct.
But there is one caveat with new nodes. For every upload the satellite selects a number of vetted nodes as well as a much smaller number of unvetted nodes. Both of those processes use the same method except for the vetted/unvetted differentiation. Afterwards if there is any overlap of subnets between those two selections one of the nodes gets dropped.

If your subnet has vetted as well as unvetted nodes, you have a chance to get selected in either of those two processes, leading to a very slight increase of total traffic until the node is vetted. Luckily this increase is so small that it’s really not worth trying to cheat this system especially since that would only work until the other node is vetted.

2 Likes

19Jul2020:
Node 1:

Node 2:

1 Like

here are the numbers for the 19th

170GB of ingress isn’t too bad ! haha

1 Like

@TheMightyGreek still ahead of the pack… and it’s 180gb ingress for you and 158-160 for the rest of us…

1 Like

testing new text formatting - stolen from Alexey :upside_down_face:

Date IngressT EgressT [GB] StoredT [TB] egress ‰ egressT EgressT [kb/s /TB] Ingress1 [GB] Egress1 [GB] Stored1 [GB] Egress1 ‰ Egress1 [kB/s] Egress1 [kB/s /TB] Ingress2 [GB] Egress2 [GB] Stored2 [GB] Egress2 ‰ Egress2 [kB/s] Egress2 [kB/s /TB]
15.07.2020 126.68 10.87 1.45 7.51 125.81 86.92 104.59 9.03 1 230 7.34 104.51 84.97 22.09 1.84 217 8.46 21.30 97.93
16.07.2020 125.09 10.96 1.57 6.98 126.89 80.84 102.43 9.18 1 330 6.90 106.28 79.91 22.66 1.78 240 7.43 20.60 85.96
17.07.2020 132.50 11.67 1.69 6.92 135.07 80.04 107.99 9.73 1 420 6.85 112.62 79.31 24.51 1.94 268 7.25 22.45 83.92
18.07.2020 141.28 12.30 1.84 6.69 142.38 77.38 73.88 8.19 1 500 5.46 94.81 63.21 67.4 4.11 340 12.09 47.57 139.91
19.07.2020 158.45 14.14 2.00 7.06 163.70 81.77 80.63 8.79 1 580 5.57 101.78 64.42 77.82 5.35 422 12.68 61.92 146.73

I have also noticed the increase in ingress…
“T” is for total “1” and “2” stand for nodes 1, nodes 2
Wanted to point out that my 10 days older node has much smaller egress than new one (you can compare it, when you scroll to the right)
Theories
1… More recent data is accessed more frequently?
2… That egress is “in fact” just “verification/confirmation info” for data received, and it is no indication how much egress will be generated when node fills up

1 Like

i don’t like the kb/s
i mean whats the point… one will not utilize it to calculate space used, so what would one use it for… only thing i can come up with is how much internet bandwidth is used, because really daily ingress can easily be divided into the avg kb/s

so if we are only using it for comparing to internet bandwidth usage, then it would make more sense to simply write it in mbit/s so that people can more easily see if it’s exceeds their internet bandwidth.

then it atleast has a purpose.

i think the model striker43 uses is much more easy to read… even if he also uses the useless kb/s

i know people find a speed gauge very fascinating… i’m just like so, but the daily ingress is essentially the exact same number… it’s a fixed avg over a preset time…
so if we are trying to streamline the information kept in the, as there is plenty of useful information to write into such a list…

1 Like

I personally think that it’s better to put emphasis on the total numbers like in @shoofar 's model because at the end of the day that’s what we use to figure out the egress permille.
As for the kb/s, it might be useful for people with very limited bandwidth to see how much head room they have but otherwise it’s pretty much an aesthetic feature.
Also putting it in mbps might be better as it’s pretty much the standard to measure internet speed.