Superzoom speed problem
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Help with my Plusnet services
- :
- Broadband
- :
- Superzoom speed problem
Re: Superzoom speed problem
27-08-2013 4:10 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: Superzoom speed problem
27-08-2013 4:43 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Turning off hardware acceleration didn't help.
Ex-Broadband Service Manager
Re: Superzoom speed problem
27-08-2013 4:57 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Much more interesting than the original!
Re: Superzoom speed problem
27-08-2013 5:49 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: Superzoom speed problem
27-08-2013 6:12 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
[Edit] I'll admit it means nothing to me
At any given moment in the universe many things happen. Coincidence is a matter of how close these events are in space, time and relationship.
Opinions expressed in forum posts are those of the poster, others may have different views.
Re: Superzoom speed problem
27-08-2013 7:17 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
@ Superzoom - Have you tried different machines to compare performance on sites?
Re: Superzoom speed problem
28-08-2013 1:10 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Yes, it's not a single-machine issue.
@w23
Thanks for checking
The network tool is pretty straightforward. It just adds a line for each http request in the order they are made, without concerning itself directly with javascript execution times or events. There is an overall waterfall timeline, and the colours break the timing of each request down into stages (which can be seen in detail by clicking a line, then selecting the timings tab on the right): DNS resolution, Connecting, Sending, Waiting, Receiving. Interpretation can be less straightforward because you can't necessarily tell from a client perspective what is causing any delay - if you control the server as well, for instance, you can see how quickly it executed its side of the transaction. But the tool provides a usefully network-centric view of things, and if significant delays are occurring at different request stages and across different servers and types of site, regardless of client, then those delays are being introduced by the network. Somewhere.
Re: Superzoom speed problem
29-08-2013 11:04 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Ex-Broadband Service Manager
Re: Superzoom speed problem
30-08-2013 2:46 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
What are you looking for in the pcaps?
Shall I upload them to a ticket?
Re: Superzoom speed problem
30-08-2013 3:30 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Ex-Broadband Service Manager
Re: Superzoom speed problem
30-08-2013 4:36 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Just the one site, and just the html element.
Re: Superzoom speed problem
01-09-2013 1:06 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
PlusNet's traffic shaper is intercepting connections, introducing delays and screwing up the TCP window size, isn't it?
Just by-the-by, port 53 UDP traffic latency and variability is pretty terrible today too:
[tt]Nameserver Response Time (ms) over 10 cached lookups
min avg max stdev retries
212.159.6.9 8.77 16.55 19.23 3.92 0
212.159.6.10 8.67 16.59 18.83 3.97 0
212.159.13.49 17.97 18.72 19.46 0.48 0
212.159.13.50 9.45 16.75 18.75 3.65 0
208.67.222.222 8.63 10.60 18.05 3.72 0
208.67.220.220 8.45 8.73 9.02 0.18 0
8.8.8.8 18.75 18.85 19.09 0.12 0
8.8.4.4 18.01 18.72 19.49 0.47 0
4.2.2.1 8.74 12.68 18.65 4.76 0
4.2.2.6 8.74 8.77 8.84 0.04 0
[/tt]
Not something reflected in ICMP, interestingly:
[tt]Pinging 212.159.13.49 with 32 bytes of data:
Reply from 212.159.13.49: bytes=32 time=5ms TTL=250
Reply from 212.159.13.49: bytes=32 time=5ms TTL=250
Reply from 212.159.13.49: bytes=32 time=5ms TTL=250
Reply from 212.159.13.49: bytes=32 time=4ms TTL=250
Reply from 212.159.13.49: bytes=32 time=5ms TTL=250
Reply from 212.159.13.49: bytes=32 time=4ms TTL=250
Reply from 212.159.13.49: bytes=32 time=4ms TTL=250
Reply from 212.159.13.49: bytes=32 time=5ms TTL=250
Reply from 212.159.13.49: bytes=32 time=5ms TTL=250
Reply from 212.159.13.49: bytes=32 time=4ms TTL=250
Ping statistics for 212.159.13.49:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 4ms[/tt]
[tt]Pinging 4.2.2.1 with 32 bytes of data:
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Reply from 4.2.2.1: bytes=32 time=4ms TTL=55
Ping statistics for 4.2.2.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 4ms, Average = 4ms[/tt]
Re: Superzoom speed problem
01-09-2013 2:43 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
sudo hping3 -S -p 53 -c 20 212.159.6.10
HPING 212.159.6.10 (eth0 212.159.6.10): S set, 40 headers + 0 data bytes
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=0 win=5840 rtt=17.7 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=1 win=5840 rtt=17.8 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=2 win=5840 rtt=17.6 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=3 win=5840 rtt=17.0 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=4 win=5840 rtt=17.9 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=5 win=5840 rtt=18.0 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=6 win=5840 rtt=17.3 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=7 win=5840 rtt=17.5 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=8 win=5840 rtt=18.1 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=9 win=5840 rtt=18.2 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=10 win=5840 rtt=17.5 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=11 win=5840 rtt=18.0 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=12 win=5840 rtt=17.5 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=13 win=5840 rtt=17.3 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=14 win=5840 rtt=17.6 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=15 win=5840 rtt=17.8 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=16 win=5840 rtt=17.0 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=17 win=5840 rtt=17.6 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=18 win=5840 rtt=18.0 ms
len=46 ip=212.159.6.10 ttl=58 DF id=0 sport=53 flags=SA seq=19 win=5840 rtt=18.0 ms
--- 212.159.6.10 hping statistic ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 17.0/17.7/18.2 ms
sudo hping3 -S -p 53 -c 20 212.159.6.9
HPING 212.159.6.9 (eth0 212.159.6.9): S set, 40 headers + 0 data bytes
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=0 win=5840 rtt=18.2 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=1 win=5840 rtt=17.7 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=2 win=5840 rtt=17.2 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=3 win=5840 rtt=17.7 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=4 win=5840 rtt=17.4 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=5 win=5840 rtt=18.4 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=6 win=5840 rtt=17.1 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=7 win=5840 rtt=17.8 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=8 win=5840 rtt=18.4 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=9 win=5840 rtt=17.9 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=10 win=5840 rtt=17.6 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=11 win=5840 rtt=17.0 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=12 win=5840 rtt=17.8 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=13 win=5840 rtt=17.1 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=14 win=5840 rtt=17.9 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=15 win=5840 rtt=17.7 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=16 win=5840 rtt=17.7 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=17 win=5840 rtt=18.1 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=18 win=5840 rtt=18.0 ms
len=46 ip=212.159.6.9 ttl=58 DF id=0 sport=53 flags=SA seq=19 win=5840 rtt=17.6 ms
--- 212.159.6.9 hping statistic ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 17.0/17.7/18.4 ms
sudo hping3 -S -p 53 -c 20 212.159.13.49
HPING 212.159.13.49 (eth0 212.159.13.49): S set, 40 headers + 0 data bytes
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=0 win=5840 rtt=17.2 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=1 win=5840 rtt=17.9 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=2 win=5840 rtt=17.6 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=3 win=5840 rtt=17.8 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=4 win=5840 rtt=17.6 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=5 win=5840 rtt=17.4 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=6 win=5840 rtt=17.7 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=7 win=5840 rtt=17.9 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=8 win=5840 rtt=17.5 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=9 win=5840 rtt=17.5 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=10 win=5840 rtt=17.6 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=11 win=5840 rtt=17.2 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=12 win=5840 rtt=17.5 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=13 win=5840 rtt=17.8 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=14 win=5840 rtt=17.8 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=15 win=5840 rtt=17.4 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=16 win=5840 rtt=17.5 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=17 win=5840 rtt=17.9 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=18 win=5840 rtt=18.0 ms
len=46 ip=212.159.13.49 ttl=58 DF id=0 sport=53 flags=SA seq=19 win=5840 rtt=17.9 ms
--- 212.159.13.49 hping statistic ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 17.2/17.6/18.0 ms
sudo hping3 -S -p 53 -c 20 212.159.13.50
HPING 212.159.13.50 (eth0 212.159.13.50): S set, 40 headers + 0 data bytes
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=0 win=5840 rtt=18.0 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=1 win=5840 rtt=17.6 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=2 win=5840 rtt=17.6 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=3 win=5840 rtt=17.4 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=4 win=5840 rtt=17.2 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=5 win=5840 rtt=17.5 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=6 win=5840 rtt=17.9 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=7 win=5840 rtt=16.9 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=8 win=5840 rtt=17.3 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=9 win=5840 rtt=17.5 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=10 win=5840 rtt=17.5 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=11 win=5840 rtt=18.0 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=12 win=5840 rtt=17.9 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=13 win=5840 rtt=17.5 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=14 win=5840 rtt=17.2 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=15 win=5840 rtt=17.4 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=16 win=5840 rtt=17.5 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=17 win=5840 rtt=17.4 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=18 win=5840 rtt=17.7 ms
len=46 ip=212.159.13.50 ttl=58 DF id=0 sport=53 flags=SA seq=19 win=5840 rtt=17.4 ms
--- 212.159.13.50 hping statistic ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 16.9/17.5/18.0 ms
pi@raspberrypi ~ $ sudo hping3 -S -p 53 -c 20 208.67.222.222
HPING 208.67.222.222 (eth0 208.67.222.222): S set, 40 headers + 0 data bytes
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=0 win=5840 rtt=17.4 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=1 win=5840 rtt=17.4 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=2 win=5840 rtt=17.0 ms
len=46 ip=208.67.222.222 ttl=54 DF id= sport=53 flags=SA seq=3 win=5840 rtt=17.3 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=4 win=5840 rtt=17.1 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=5 win=5840 rtt=19.0 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=6 win=5840 rtt=17.0 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=7 win=5840 rtt=17.2 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=8 win=5840 rtt=17.6 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=9 win=5840 rtt=17.5 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=10 win=5840 rtt=17.8 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=11 win=5840 rtt=17.0 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=12 win=5840 rtt=17.4 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=13 win=5840 rtt=17.1 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=14 win=5840 rtt=17.5 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=15 win=5840 rtt=17.2 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=16 win=5840 rtt=17.0 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=17 win=5840 rtt=17.5 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=18 win=5840 rtt=17.3 ms
len=46 ip=208.67.222.222 ttl=54 DF id=0 sport=53 flags=SA seq=19 win=5840 rtt=18.3 ms
--- 208.67.222.222 hping statistic ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 17.0/17.4/19.0 ms
sudo hping3 -S -p 53 -c 20 208.67.222.220
HPING 208.67.222.220 (eth0 208.67.222.220): S set, 40 headers + 0 data bytes
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=0 win=5840 rtt=17.5 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=1 win=5840 rtt=17.5 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=2 win=5840 rtt=16.9 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=3 win=5840 rtt=17.1 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=4 win=5840 rtt=17.5 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=5 win=5840 rtt=17.6 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=6 win=5840 rtt=17.0 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=7 win=5840 rtt=16.8 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=8 win=5840 rtt=17.6 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=9 win=5840 rtt=17.4 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=10 win=5840 rtt=17.5 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=11 win=5840 rtt=17.7 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=12 win=5840 rtt=17.5 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=13 win=5840 rtt=17.1 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=14 win=5840 rtt=17.4 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=15 win=5840 rtt=17.8 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=16 win=5840 rtt=16.9 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=17 win=5840 rtt=17.1 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=18 win=5840 rtt=17.4 ms
len=46 ip=208.67.222.220 ttl=54 DF id=0 sport=53 flags=SA seq=19 win=5840 rtt=17.4 ms
--- 208.67.222.220 hping statistic ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 16.8/17.3/17.8 ms
sudo hping3 -S -p 53 -c 20 8.8.8.8
HPING 8.8.8.8 (eth0 8.8.8.8): S set, 40 headers + 0 data bytes
len=46 ip=8.8.8.8 ttl=46 id=13635 sport=53 flags=SA seq=0 win=62920 rtt=26.6 ms
len=46 ip=8.8.8.8 ttl=46 id=56979 sport=53 flags=SA seq=1 win=62920 rtt=27.2 ms
len=46 ip=8.8.8.8 ttl=46 id=63544 sport=53 flags=SA seq=2 win=62920 rtt=26.4 ms
len=46 ip=8.8.8.8 ttl=46 id=63545 sport=53 flags=SA seq=3 win=62920 rtt=27.8 ms
len=46 ip=8.8.8.8 ttl=47 id=3805 sport=53 flags=SA seq=4 win=62920 rtt=26.1 ms
len=46 ip=8.8.8.8 ttl=47 id=56980 sport=53 flags=SA seq=5 win=62920 rtt=26.1 ms
len=46 ip=8.8.8.8 ttl=47 id=56981 sport=53 flags=SA seq=6 win=62920 rtt=26.1 ms
len=46 ip=8.8.8.8 ttl=46 id=56982 sport=53 flags=SA seq=7 win=62920 rtt=26.5 ms
len=46 ip=8.8.8.8 ttl=46 id=18169 sport=53 flags=SA seq=8 win=62920 rtt=26.5 ms
len=46 ip=8.8.8.8 ttl=47 id=18170 sport=53 flags=SA seq=9 win=62920 rtt=26.6 ms
len=46 ip=8.8.8.8 ttl=47 id=56983 sport=53 flags=SA seq=10 win=62920 rtt=26.5 ms
len=46 ip=8.8.8.8 ttl=47 id=18171 sport=53 flags=SA seq=11 win=62920 rtt=26.5 ms
len=46 ip=8.8.8.8 ttl=46 id=36504 sport=53 flags=SA seq=12 win=62920 rtt=26.1 ms
len=46 ip=8.8.8.8 ttl=47 id=56984 sport=53 flags=SA seq=13 win=62920 rtt=26.1 ms
len=46 ip=8.8.8.8 ttl=47 id=56985 sport=53 flags=SA seq=14 win=62920 rtt=26.1 ms
len=46 ip=8.8.8.8 ttl=47 id=41664 sport=53 flags=SA seq=15 win=42900 rtt=26.3 ms
len=46 ip=8.8.8.8 ttl=47 id=41665 sport=53 flags=SA seq=16 win=42900 rtt=26.1 ms
len=46 ip=8.8.8.8 ttl=47 id=56986 sport=53 flags=SA seq=17 win=62920 rtt=25.7 ms
len=46 ip=8.8.8.8 ttl=46 id=3806 sport=53 flags=SA seq=18 win=62920 rtt=26.2 ms
len=46 ip=8.8.8.8 ttl=46 id=56987 sport=53 flags=SA seq=19 win=62920 rtt=26.5 ms
--- 8.8.8.8 hping statistic ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 25.7/26.4/27.8 ms
sudo hping3 -S -p 53 -c 20 8.8.4.4
HPING 8.8.4.4 (eth0 8.8.4.4): S set, 40 headers + 0 data bytes
len=46 ip=8.8.4.4 ttl=46 id=56979 sport=53 flags=SA seq=0 win=62920 rtt=26.4 ms
len=46 ip=8.8.4.4 ttl=47 id=42929 sport=53 flags=SA seq=1 win=62920 rtt=26.4 ms
len=46 ip=8.8.4.4 ttl=46 id=56980 sport=53 flags=SA seq=2 win=62920 rtt=26.4 ms
len=46 ip=8.8.4.4 ttl=46 id=17072 sport=53 flags=SA seq=3 win=62920 rtt=26.0 ms
len=46 ip=8.8.4.4 ttl=46 id=3805 sport=53 flags=SA seq=4 win=62920 rtt=26.2 ms
len=46 ip=8.8.4.4 ttl=46 id=3806 sport=53 flags=SA seq=5 win=62920 rtt=26.3 ms
len=46 ip=8.8.4.4 ttl=47 id=37969 sport=53 flags=SA seq=6 win=62920 rtt=26.3 ms
len=46 ip=8.8.4.4 ttl=47 id=3807 sport=53 flags=SA seq=7 win=62920 rtt=26.6 ms
len=46 ip=8.8.4.4 ttl=46 id=17073 sport=53 flags=SA seq=8 win=62920 rtt=26.6 ms
len=46 ip=8.8.4.4 ttl=47 id=37970 sport=53 flags=SA seq=9 win=62920 rtt=26.3 ms
len=46 ip=8.8.4.4 ttl=47 id=36504 sport=53 flags=SA seq=10 win=62920 rtt=26.1 ms
len=46 ip=8.8.4.4 ttl=47 id=3808 sport=53 flags=SA seq=11 win=62920 rtt=26.1 ms
len=46 ip=8.8.4.4 ttl=46 id=36505 sport=53 flags=SA seq=12 win=62920 rtt=26.4 ms
len=46 ip=8.8.4.4 ttl=47 id=37971 sport=53 flags=SA seq=13 win=62920 rtt=26.4 ms
len=46 ip=8.8.4.4 ttl=46 id=3809 sport=53 flags=SA seq=14 win=62920 rtt=25.9 ms
len=46 ip=8.8.4.4 ttl=46 id=56981 sport=53 flags=SA seq=15 win=62920 rtt=26.9 ms
len=46 ip=8.8.4.4 ttl=46 id=42930 sport=53 flags=SA seq=16 win=62920 rtt=26.3 ms
len=46 ip=8.8.4.4 ttl=46 id=3810 sport=53 flags=SA seq=17 win=62920 rtt=26.6 ms
len=46 ip=8.8.4.4 ttl=46 id=37972 sport=53 flags=SA seq=18 win=62920 rtt=26.1 ms
len=46 ip=8.8.4.4 ttl=46 id=17074 sport=53 flags=SA seq=19 win=62920 rtt=26.3 ms
--- 8.8.4.4 hping statistic ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 25.9/26.3/26.9 ms
pi@raspberrypi ~ $ sudo hping3 -S -p 53 -c 20 4.2.2.1
HPING 4.2.2.1 (eth0 4.2.2.1): S set, 40 headers + 0 data bytes
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=0 win=5840 rtt=17.5 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=1 win=5840 rtt=17.0 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=2 win=5840 rtt=17.1 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=3 win=5840 rtt=16.9 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=4 win=5840 rtt=16.5 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=5 win=5840 rtt=17.0 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=6 win=5840 rtt=17.0 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=7 win=5840 rtt=17.5 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=8 win=5840 rtt=17.5 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=9 win=5840 rtt=17.4 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=10 win=5840 rtt=17.5 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=11 win=5840 rtt=17.2 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=12 win=5840 rtt=16.8 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=13 win=5840 rtt=17.1 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=14 win=5840 rtt=17.2 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=15 win=5840 rtt=17.0 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=16 win=5840 rtt=17.3 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=17 win=5840 rtt=17.3 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=18 win=5840 rtt=17.6 ms
len=46 ip=4.2.2.1 ttl=55 DF id=0 sport=53 flags=SA seq=19 win=5840 rtt=16.9 ms
--- 4.2.2.1 hping statistic ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 16.5/17.2/17.6 ms
This server is dropping packets?????
sudo hping3 -S -p 53 -c 20 4.2.2.6
HPING 4.2.2.6 (eth0 4.2.2.6): S set, 40 headers + 0 data bytes
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=1 win=5840 rtt=17.7 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=5 win=5840 rtt=17.0 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=7 win=5840 rtt=16.8 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=8 win=5840 rtt=17.0 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=9 win=5840 rtt=17.3 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=10 win=5840 rtt=17.2 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=11 win=5840 rtt=17.3 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=12 win=5840 rtt=17.6 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=14 win=5840 rtt=16.8 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=16 win=5840 rtt=16.7 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=17 win=5840 rtt=16.9 ms
len=46 ip=4.2.2.6 ttl=55 DF id=0 sport=53 flags=SA seq=18 win=5840 rtt=17.0 ms
--- 4.2.2.6 hping statistic ---
20 packets transmitted, 12 packets received, 40% packet loss
round-trip min/avg/max = 16.7/17.1/17.7 ms
raspberrypi ~ $ ping -c 10 212.159.13.49
PING 212.159.13.49 (212.159.13.49) 56(84) bytes of data.
64 bytes from 212.159.13.49: icmp_req=1 ttl=250 time=17.7 ms
64 bytes from 212.159.13.49: icmp_req=2 ttl=250 time=17.3 ms
64 bytes from 212.159.13.49: icmp_req=3 ttl=250 time=16.8 ms
64 bytes from 212.159.13.49: icmp_req=4 ttl=250 time=18.0 ms
64 bytes from 212.159.13.49: icmp_req=5 ttl=250 time=16.8 ms
64 bytes from 212.159.13.49: icmp_req=6 ttl=250 time=17.3 ms
64 bytes from 212.159.13.49: icmp_req=7 ttl=250 time=17.1 ms
64 bytes from 212.159.13.49: icmp_req=8 ttl=250 time=16.9 ms
64 bytes from 212.159.13.49: icmp_req=9 ttl=250 time=16.8 ms
64 bytes from 212.159.13.49: icmp_req=10 ttl=250 time=16.9 ms
--- 212.159.13.49 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 16.819/17.214/18.036/0.431 ms
raspberrypi ~ $ ping -c 10 4.2.2.1
PING 4.2.2.1 (4.2.2.1) 56(84) bytes of data.
64 bytes from 4.2.2.1: icmp_req=1 ttl=55 time=17.3 ms
64 bytes from 4.2.2.1: icmp_req=2 ttl=55 time=16.4 ms
64 bytes from 4.2.2.1: icmp_req=3 ttl=55 time=16.6 ms
64 bytes from 4.2.2.1: icmp_req=4 ttl=55 time=16.6 ms
64 bytes from 4.2.2.1: icmp_req=5 ttl=55 time=16.8 ms
64 bytes from 4.2.2.1: icmp_req=6 ttl=55 time=16.8 ms
64 bytes from 4.2.2.1: icmp_req=7 ttl=55 time=16.5 ms
64 bytes from 4.2.2.1: icmp_req=8 ttl=55 time=16.8 ms
64 bytes from 4.2.2.1: icmp_req=9 ttl=55 time=16.7 ms
64 bytes from 4.2.2.1: icmp_req=10 ttl=55 time=16.3 ms
--- 4.2.2.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9014ms
rtt min/avg/max/mdev = 16.362/16.722/17.336/0.288 ms
I'm just using a plain ole raspberry pi not doing anything other than dns and testing, i can't replicate your efforts though
Re: Superzoom speed problem
01-09-2013 2:50 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Quote from: SuperZoom
PlusNet's traffic shaper is intercepting connections, introducing delays and screwing up the TCP window size, isn't it?
That's a pretty bold statement. Aren't you trying to compare two totally different things (name server address resolution vs ICMP pings)?
What you posted looks consistent with mine (I use OpenDNS):
Minimum (Ms)
Maximum (Ms)
Average (Ms)
2013-09-01 4.69 18.35 5.56
2013-08-31 4.50 17.55 7.33
2013-08-30 4.57 25.41 7.80
2013-08-29 4.41 16.72 5.85
2013-08-28 4.53 14.35 5.65
2013-08-27 4.63 26.82 8.23
2013-08-26 4.56 7.53 5.28
2013-08-25 4.38 17.62 5.80
Re: Superzoom speed problem
01-09-2013 3:10 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I thought the Firefox Developer Tools Network screenshots in the videos indicated SuperZoom's FTTP connection was somehow managing to take longer to load a webpage than my 3Mb Plusnet ADSL!
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page