[img]Download Failed (1)[/img]
well after the weekend showed no issues I stayed on pc late today and have done some testing whilst its spiking.
pingtest.net still only showing 3ms jitter but reports packet loss
ssh has a jumping cursor, not that bad but its happening. Also when the cursor is not jumping there is noticeble jitter compared to off peak. So basically my port is struggling on capacity that is supposed to handle uplifted speeds but speeds are not uplifted yet. This also whilst traffic shaped both directions.
My thoughts are and its only a guess, that the vmng300 has a smaller queue size to the UBR and its why we see lower latency on it, but during congestion and/or high local utilisation it behaves different as a result.
I think my service is going to get rough when the speeds get uplifted unless there is another bandwidth upgrade before then for me.
Speedtests are ok but do ramp up slower than usual, stay at max once ramped up.
I also have had some feedback in regards to how the vmng300 handles bonding compared to the superhub.
What I was told is this.
If a channel gets congested on the superhub regardless of utilisation it will auto balance to a lower utilised channel, on the vmng300 it will only do so if packets are been dropped (speed affected). I tested this now and after I did a speedtest the tbb graph settled down to lower jitter again. Can see the big blue spike just after 10pm (speedtest) followed by flatter yellow and thinner blue again.