![]() |
Re: Think Broadband Ping Monitor Results (POST YOURS)
Quote:
|
Re: Think Broadband Ping Monitor Results (POST YOURS)
Well, holidays have begun, and as soon as I want to spend some time gaming. This is what I get.
http://www.thinkbroadband.com/ping/s...17-04-2011.png Usually not this bad. But this is not the norm for me. :/ |
Re: Think Broadband Ping Monitor Results (POST YOURS)
Quote:
strangely enough dispite pip trying to push it along for me samknows are still ignoring my request. I have yet to see someone in a high utilised area been accepted for this trial. |
Re: Think Broadband Ping Monitor Results (POST YOURS)
Funny you should say that Chrys, I tried getting on it too, twice in fact but I've just been ignored......
|
Re: Think Broadband Ping Monitor Results (POST YOURS)
Quote:
|
Re: Think Broadband Ping Monitor Results (POST YOURS)
[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. |
Re: Think Broadband Ping Monitor Results (POST YOURS)
Quote:
|
Re: Think Broadband Ping Monitor Results (POST YOURS)
check my edit, I added some info as to why I wasnt seeing spikes when utilising the connection.
|
Re: Think Broadband Ping Monitor Results (POST YOURS)
same again tonight was idlish connection spiking high during peak.
10 pings. Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data: Reply from 212.58.224.138: bytes=32 time=14ms TTL=117 Reply from 212.58.224.138: bytes=32 time=13ms TTL=117 Reply from 212.58.224.138: bytes=32 time=15ms TTL=117 Reply from 212.58.224.138: bytes=32 time=41ms TTL=117 Reply from 212.58.224.138: bytes=32 time=20ms TTL=117 Reply from 212.58.224.138: bytes=32 time=14ms TTL=117 Reply from 212.58.224.138: bytes=32 time=16ms TTL=117 Reply from 212.58.224.138: bytes=32 time=14ms TTL=117 Reply from 212.58.224.138: bytes=32 time=16ms TTL=117 Reply from 212.58.224.138: bytes=32 time=13ms TTL=117 Ping statistics for 212.58.224.138: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 41ms, Average = 17ms then run speedtest, graph goes to low spikes again. 10 more pings. Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data: Reply from 212.58.224.138: bytes=32 time=16ms TTL=117 Reply from 212.58.224.138: bytes=32 time=14ms TTL=117 Reply from 212.58.224.138: bytes=32 time=16ms TTL=117 Reply from 212.58.224.138: bytes=32 time=14ms TTL=117 Reply from 212.58.224.138: bytes=32 time=16ms TTL=117 Reply from 212.58.224.138: bytes=32 time=15ms TTL=117 Reply from 212.58.224.138: bytes=32 time=13ms TTL=117 Reply from 212.58.224.138: bytes=32 time=15ms TTL=117 Reply from 212.58.224.138: bytes=32 time=13ms TTL=117 Reply from 212.58.224.138: bytes=32 time=14ms TTL=117 Ping statistics for 212.58.224.138: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 16ms, Average = 14ms |
Re: Think Broadband Ping Monitor Results (POST YOURS)
I've noticed a bit of a drop with my Infinity presumably due to the kids hols.
Using BT's own speedtester. Test1 comprises of two tests 1. Best Effort Test: -provides background information. Download Speed 33886 Kbps 38717 Kbps Max Achievable Speed > Download speedachieved during the test was - 33886 Kbps For your connection, the acceptable range of speeds is 12000-38717 Kbps . Additional Information: IP Profile for your line is - 38717 Kbps 2. Upstream Test: -provides background information. Upload Speed 7959 Kbps 10000 Kbps Max Achievable Speed Speedtest.net https://www.cableforum.co.uk/images/...2011/04/47.png Think I should complain?:D:D:D |
Re: Think Broadband Ping Monitor Results (POST YOURS)
10 pings on superhub.
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data: Reply from 212.58.224.138: bytes=32 time=14ms TTL=119 Reply from 212.58.224.138: bytes=32 time=27ms TTL=119 Reply from 212.58.224.138: bytes=32 time=14ms TTL=119 Reply from 212.58.224.138: bytes=32 time=12ms TTL=119 Reply from 212.58.224.138: bytes=32 time=15ms TTL=119 Reply from 212.58.224.138: bytes=32 time=15ms TTL=119 Reply from 212.58.224.138: bytes=32 time=28ms TTL=119 Reply from 212.58.224.138: bytes=32 time=15ms TTL=119 Reply from 212.58.224.138: bytes=32 time=25ms TTL=119 Reply from 212.58.224.138: bytes=32 time=15ms TTL=119 Ping statistics for 212.58.224.138: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 28ms, Average = 18ms live graph. This only be up probably whilst I test new firmware tho. https://www.cableforum.co.uk/images/...2011/04/46.png |
Re: Think Broadband Ping Monitor Results (POST YOURS)
http://www.thinkbroadband.com/ping/s...0-04-2011.html
http://www.thinkbroadband.com/ping/s...20-04-2011.png Finally got my Sky BB up and running, only getting about about 3.5Mbps DL and 0.4 Up at the moment but what a diference The ping is quite high due to my distance from the exchange but it's only to the first hop and gaming on it is world's apart, I played Black Op's on the PS3 for a hour last night and the only bit of lag I got was when a mate hosted (on Virgin) but that only lasted for a second or two plus no more getting shot round corners, no dropped bullets whilst sniping etc etc. It just goes to show that Jitter makes all the difference. I've not had any signing in issues or error codes, voice quality whilst in game has improved with friends saying they can hear me clearer. I dont know why the monitor stopped working ????? Any ideas as I wasn't even in the house when it stopped, and the IP addy hasnt changed. |
Re: Think Broadband Ping Monitor Results (POST YOURS)
that line must have some kind of extreme interleaving enabled.
|
Re: Think Broadband Ping Monitor Results (POST YOURS)
Quote:
---------- Post added at 09:33 ---------- Previous post was at 08:42 ---------- I will apologise now as I know sweet FA about ADSL broadband |
Re: Think Broadband Ping Monitor Results (POST YOURS)
interleaving is a buffer added to add error correction, the higher its set then more latency the connection has. High interleaving will add a lot of latency and can easily triple base latency.
|
All times are GMT +1. The time now is 21:52. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2025, vBulletin Solutions Inc.
All Posts and Content are © Cable Forum