50M : Installed Finally But...

[Ignitionnet]

Originally Posted by Chrysalis

ignition see when you the victim it looks a bit different?

Nope - I'm more amused than anything else. I would be quite happy to sympathise with anyone seeing 10% speeds, a little jitter I was fine with.

I'll see what the Samknows box I forgot I had has to say before I get too indignant. I suspect the reading isn't accurate as at that speed pages should load like sludge but aren't.

[craigj2k12]

Originally Posted by Chrysalis

in my view the modem side of the superhub is fine, I dont think its the cause of your issue. But I havent used it on the 50mbit service. A vmng300 would probably show lower latency/jitter tho but also along with bursts of bigger spikes when congestion gets too much as well as occasional bursts of packet loss. For speedtests I find the vmng300 made no difference but did affect things like web browsing speed and streaming performance.

as we have discussed it uses a different minislot size and thats about it

[Chrysalis]

Originally Posted by Ignitionnet

Nope - I'm more amused than anything else. I would be quite happy to sympathise with anyone seeing 10% speeds, a little jitter I was fine with.

I'll see what the Samknows box I forgot I had has to say before I get too indignant. I suspect the reading isn't accurate as at that speed pages should load like sludge but aren't.

Well this is it, if things ever get congested enough that a lot of jitter shows the chances are speeds are also going to be severely compromised so a lot of jitter indicates underlying congestion issues (I know not always the case), arguable same with variable speed, if you see varying speed down to say 80% then my guess is the chances are its not going to be consistently around 80% you would see larger swings. It seems with VM things are either fine or very bad. I do agree with you small jitter is ok and have accepted my current service as fine even with its small jitter. Its when I had large jitter I had issues with it but that was also alongside speed problems as the 2 seem to go hand in hand.

[Ignitionnet]

How about jitter like this Chrys?

Pinging 194.168.4.100 with 32 bytes of data:
Reply from 194.168.4.100: bytes=32 time=48ms TTL=251
Reply from 194.168.4.100: bytes=32 time=53ms TTL=251
Reply from 194.168.4.100: bytes=32 time=735ms TTL=251
Reply from 194.168.4.100: bytes=32 time=750ms TTL=251
Request timed out.
Reply from 194.168.4.100: bytes=32 time=15ms TTL=251
Reply from 194.168.4.100: bytes=32 time=26ms TTL=251
Reply from 194.168.4.100: bytes=32 time=41ms TTL=251
Reply from 194.168.4.100: bytes=32 time=19ms TTL=251
Reply from 194.168.4.100: bytes=32 time=43ms TTL=251

Ping statistics for 194.168.4.100:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 750ms, Average = 192ms

[Chrysalis]

yep thats too high in my book. Sorry if you disagree but when I last had jitter that high it accompanied speed issues. The way VM run their network I dont think you would get that high jitter without speed issues.

mine below 2 mins ago taken.

C:\>ping -n 10 bbc.co.uk

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=13ms TTL=117
Reply from 212.58.224.138: bytes=32 time=15ms TTL=117
Reply from 212.58.224.138: bytes=32 time=14ms TTL=117
Reply from 212.58.224.138: bytes=32 time=19ms TTL=117
Reply from 212.58.224.138: bytes=32 time=12ms TTL=117
Reply from 212.58.224.138: bytes=32 time=14ms TTL=117
Reply from 212.58.224.138: bytes=32 time=14ms TTL=117
Reply from 212.58.224.138: bytes=32 time=14ms TTL=117
Reply from 212.58.224.138: bytes=32 time=17ms TTL=117

---------- Post added at 21:32 ---------- Previous post was at 21:32 ----------

for the dns server.

C:\>ping -n 10 194.168.4.100

Pinging 194.168.4.100 with 32 bytes of data:
Reply from 194.168.4.100: bytes=32 time=8ms TTL=252
Reply from 194.168.4.100: bytes=32 time=9ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=8ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=7ms TTL=252
Reply from 194.168.4.100: bytes=32 time=6ms TTL=252

Ping statistics for 194.168.4.100:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 9ms, Average = 7ms

[pip08456]

Sorry Igni, couldn't resist.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>ping 194.168.4.100

Pinging 194.168.4.100 with 32 bytes of data:

Reply from 194.168.4.100: bytes=32 time=16ms TTL=239
Reply from 194.168.4.100: bytes=32 time=16ms TTL=239
Reply from 194.168.4.100: bytes=32 time=15ms TTL=239
Reply from 194.168.4.100: bytes=32 time=16ms TTL=239

Ping statistics for 194.168.4.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 16ms, Average = 15ms

[Chrysalis]

also you seem to have packetloss on docsis3? going from bad to worse.

---------- Post added at 21:36 ---------- Previous post was at 21:35 ----------

heh pip I think ignition probably got an exploding head at the moment.

[jb66]

Pinging 194.168.4.100 with 32 bytes of data:
Reply from 194.168.4.100: bytes=32 time=10ms TTL=252
Reply from 194.168.4.100: bytes=32 time=19ms TTL=252
Reply from 194.168.4.100: bytes=32 time=8ms TTL=252
Reply from 194.168.4.100: bytes=32 time=10ms TTL=252

Ping statistics for 194.168.4.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 19ms, Average = 11ms

and thats with a superdud on wifi!!!

[pip08456]

Like Igni I'm finding it humourous ATM. It will be interesting to see what excuses VM give him.

[Ignitionnet]

Never mind... welcome Igni to VM

Broadband feature interruptions
The following issues may be affecting some aspects of your Virgin Media Broadband service.
You will currently be experiencing a loss of TV & broadband internet services. Our engineers are aware of this issue and are currently working to fix it fast. We apologise for any inconvenience this may be causing.
Date Issue raised:May 06 2011, 20:45
Estimated repair time:May 07 2011, 00:45
Fault reference:F001596899

[Chrysalis]

was that raised by you? the start time is not long ago.

[pip08456]

You could nip down to the UBR and give them a hand!

[Ignitionnet]

Originally Posted by Chrysalis

was that raised by you? the start time is not long ago.

Nope nothing to do with me.

[Stephen]

Originally Posted by Ignitionnet

Why would it become more stable after a couple of days?

This isn't ADSL, it's not going to rate adapt to try and find the most stable frequencies.

I have never had to give any of a Terayon Terajet 210 on 512k, an Ambit 100 on 1Mbit, an Ambit 120 on 3Mbit, a VM 256 on 20Mbit or a VMNG300 on 50Mbit a couple of days to stabilise.

Would appreciate it if you could put a bit of meat on those bones rather than 'it may become more stable after a couple of days.' It's a fresh install, new cable pull, everything should be fastened nice and tightly and is going by the power levels.

You asked for advice and I gave you mine.

Personally speed tests are pointless. Anytime I check I don't always get my 50mb down but it's always 5mb up. However when downloading stuff it sits around 6mbps and that's via wireless so that's all that matters really.

.

[pip08456]

Originally Posted by Stephen

You asked for advice and I gave you mine.
.

And if that advice is wrong?