Jump to content

dslreprts and laptop question


Acebri

Recommended Posts

i am running dslreports to try find my best bb settings for my netduma i have a few questions 

 

1. no matter what i do on my laptop i cannot get the same speeds i get when wired to my xbox one with the same ethernet cable laptop = between 50 60 download and have the exact same settings i use for my xbox  and xbox one is always above 70 usually 74 . will this have an impact on me finding the double A s for BB. i am using 74 download and 19 upload for my netduma bandwidth spent 3 hours yesterday trying to get A A s closest i got was B, A+, D

 

2 is there a best way to find the settings currently i am going upload cap at 100% then moving my download cap from 5 to 100 testing every 5% i go up on download while keeping upload at 100 and when i reach 100%, and then i move down to 95% upload and download at 5% to 100% testing every 5% download added . sorry if its a noobies question just dont want to waste another 3-4 hours today if im doing it all wrong .my ping to london and ireland seems to be ok with me getting between 30 -70 every time.  thanks  

Link to comment
Share on other sites

The only time you need to obsess about buffer bloat is if you have family members maxing out the connection while you game, set the sliders to 70% each way to combat this and relax.

Link to comment
Share on other sites

.my ping to london and ireland seems to be ok with me getting between 30 -70 every time.  thanks  

This seem high where do you live and have you ran the netduma networks diags or ping plotter at peak times to look at how your ISP is fairing?

Link to comment
Share on other sites

This seem high where do you live and have you ran the netduma networks diags or ping plotter at peak times to look at how your ISP is fairing?

i only use the internet when playing cod . i thought getting A A on bufferbloat gave you a better connection on black ops 3 than just setting settings to 70 70 , what settings do you use for playing COD and is your connection good. l ive in a rural place in scotland ARGYLL

Link to comment
Share on other sites

I am just below you in Cumbria.

 

I have a 16ms baseline ping no jitter.

 

The only time fixing bufferbloat comes into fruition is if you have people using bandwidth or a phone updating apps etc, so setting to 70% and forgetting is how I do it as my son is always online either gaming or streaming so the CC is a god send for me.

Link to comment
Share on other sites

This seem high where do you live and have you ran the netduma networks diags or ping plotter at peak times to look at how your ISP is fairing?

 

It does seem high but on DSL Reports, my ping to London with Virgin was nearly always over 30ms, usually 35ms+ and my ping to Ireland was about 45ms.

 

And I live less than 50 miles from London. Good old Virgin.

Link to comment
Share on other sites

The only time you need to obsess about buffer bloat is if you have family members maxing out the connection while you game, set the sliders to 70% each way to combat this and relax.

Since using your advice I have stopped rubber banding in COD games , before I was using a profile made up for me anti lag comp settings and have changed my Ethernet cable that has also helped . Just another question I see a few people talking about changing this i like to game using the google dns as it lowers my ping alot , could this help lower my ping and if so how do I go about doing this via Duma router . Thanks

Link to comment
Share on other sites

Google's 8.8.8.8 DNS is having issues at the moment I would not change it.

 

Changing your DNS may speed up browsing by 1ms using a faster DNS if your lucky.

 

Anti lag comp? , we need the ping compensation that is in our games or we would be shooting into thin air, ping comp is a good thing and nothing to be combated :)

 

Great to hear that the rubber banding has stopped, enjoy your gaming :)

Link to comment
Share on other sites

Google's 8.8.8.8 DNS is having issues at the moment I would not change it.

 

Changing your DNS may speed up browsing by 1ms using a faster DNS if your lucky.

 

Anti lag comp? , we need the ping compensation that is in our games or we would be shooting into thin air, ping comp is a good thing and nothing to be combated :)

 

Great to hear that the rubber banding has stopped, enjoy your gaming :)

Annonymous kindly made me a lag comp profile based on my speeds . I only wish for a lower ping , my mates from england get a 15 ping in games with me and my ping is 40-50 in the same lobby

Link to comment
Share on other sites

That is more than likely because your base ping is much higher then theirs due to interleaving on your line.

 

Post your Netduma diags, the type of router/modem you use and what make of cabinet you are on.

 

http://www.kitz.co.uk/adsl/fttc-cabinets.htm

ftcc cabinet housings cabinet its about 5 minutes walk away , bthh5 type B 

 

wired diag

 

Ping Jitter Spikes Packet Loss Good Exceptional Exceptional Lost 8
Show Details
Ping
PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: seq=1 ttl=51 time=27.103 ms

64 bytes from 8.8.8.8: seq=4 ttl=51 time=27.082 ms

64 bytes from 8.8.8.8: seq=5 ttl=51 time=26.925 ms

64 bytes from 8.8.8.8: seq=6 ttl=51 time=27.128 ms

64 bytes from 8.8.8.8: seq=7 ttl=51 time=26.886 ms

64 bytes from 8.8.8.8: seq=8 ttl=51 time=26.927 ms

64 bytes from 8.8.8.8: seq=9 ttl=51 time=27.007 ms

64 bytes from 8.8.8.8: seq=10 ttl=51 time=26.976 ms

64 bytes from 8.8.8.8: seq=13 ttl=51 time=27.070 ms

64 bytes from 8.8.8.8: seq=14 ttl=51 time=27.045 ms

64 bytes from 8.8.8.8: seq=16 ttl=51 time=27.098 ms

64 bytes from 8.8.8.8: seq=17 ttl=51 time=26.885 ms

64 bytes from 8.8.8.8: seq=19 ttl=51 time=26.870 ms

64 bytes from 8.8.8.8: seq=20 ttl=51 time=27.097 ms

64 bytes from 8.8.8.8: seq=21 ttl=51 time=26.954 ms

64 bytes from 8.8.8.8: seq=22 ttl=51 time=27.035 ms

64 bytes from 8.8.8.8: seq=23 ttl=51 time=26.997 ms

 

--- 8.8.8.8 ping statistics ---

25 packets transmitted, 17 packets received, 32% packet loss

round-trip min/avg/max = 26.870/27.005/27.128 ms

Trace
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets

1 192.168.1.254 0.762 ms 0.625 ms 0.547 ms

2 217.32.142.197 10.507 ms 10.718 ms 10.645 ms

3 217.32.142.222 11.402 ms 11.617 ms 11.507 ms

4 212.140.206.50 18.627 ms 18.475 ms 18.413 ms

5 31.55.165.45 17.183 ms 16.684 ms 16.948 ms

6 31.55.165.107 16.799 ms 16.825 ms 17.176 ms

7 109.159.250.78 16.482 ms 109.159.250.66 16.418 ms 109.159.250.62 16.408 ms

8 109.159.250.24 27.304 ms 109.159.250.38 25.945 ms 109.159.250.36 28.450 ms

9 62.172.102.9 24.585 ms 62.172.102.13 26.158 ms 109.159.254.34 26.974 ms

10 109.159.253.67 24.784 ms 25.656 ms 26.272 ms

11 216.239.54.251 24.071 ms 72.14.234.65 25.736 ms 25.399 ms

12 74.125.37.119 28.897 ms 72.14.235.89 25.634 ms 216.239.57.129 24.676 ms

13 8.8.8.8 26.284 ms * 27.783 ms

Link to comment
Share on other sites

 

ftcc cabinet housings cabinet its about 5 minutes walk away , bthh5 type B 

 

wired diag

 

Ping Jitter Spikes Packet Loss Good Exceptional Exceptional Lost 8
Show Details
Ping
PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: seq=1 ttl=51 time=27.103 ms

64 bytes from 8.8.8.8: seq=4 ttl=51 time=27.082 ms

64 bytes from 8.8.8.8: seq=5 ttl=51 time=26.925 ms

64 bytes from 8.8.8.8: seq=6 ttl=51 time=27.128 ms

64 bytes from 8.8.8.8: seq=7 ttl=51 time=26.886 ms

64 bytes from 8.8.8.8: seq=8 ttl=51 time=26.927 ms

64 bytes from 8.8.8.8: seq=9 ttl=51 time=27.007 ms

64 bytes from 8.8.8.8: seq=10 ttl=51 time=26.976 ms

64 bytes from 8.8.8.8: seq=13 ttl=51 time=27.070 ms

64 bytes from 8.8.8.8: seq=14 ttl=51 time=27.045 ms

64 bytes from 8.8.8.8: seq=16 ttl=51 time=27.098 ms

64 bytes from 8.8.8.8: seq=17 ttl=51 time=26.885 ms

64 bytes from 8.8.8.8: seq=19 ttl=51 time=26.870 ms

64 bytes from 8.8.8.8: seq=20 ttl=51 time=27.097 ms

64 bytes from 8.8.8.8: seq=21 ttl=51 time=26.954 ms

64 bytes from 8.8.8.8: seq=22 ttl=51 time=27.035 ms

64 bytes from 8.8.8.8: seq=23 ttl=51 time=26.997 ms

 

--- 8.8.8.8 ping statistics ---

25 packets transmitted, 17 packets received, 32% packet loss

round-trip min/avg/max = 26.870/27.005/27.128 ms

Trace
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets

1 192.168.1.254 0.762 ms 0.625 ms 0.547 ms

2 217.32.142.197 10.507 ms 10.718 ms 10.645 ms

3 217.32.142.222 11.402 ms 11.617 ms 11.507 ms

4 212.140.206.50 18.627 ms 18.475 ms 18.413 ms

5 31.55.165.45 17.183 ms 16.684 ms 16.948 ms

6 31.55.165.107 16.799 ms 16.825 ms 17.176 ms

7 109.159.250.78 16.482 ms 109.159.250.66 16.418 ms 109.159.250.62 16.408 ms

8 109.159.250.24 27.304 ms 109.159.250.38 25.945 ms 109.159.250.36 28.450 ms

9 62.172.102.9 24.585 ms 62.172.102.13 26.158 ms 109.159.254.34 26.974 ms

10 109.159.253.67 24.784 ms 25.656 ms 26.272 ms

11 216.239.54.251 24.071 ms 72.14.234.65 25.736 ms 25.399 ms

12 74.125.37.119 28.897 ms 72.14.235.89 25.634 ms 216.239.57.129 24.676 ms

13 8.8.8.8 26.284 ms * 27.783 ms

 

test two 

Ping Jitter Spikes Packet Loss Good Exceptional Exceptional Lost 3
Show Details
Ping
PING 8.8.8.8 (8.8.8.8): 56 data bytes

64 bytes from 8.8.8.8: seq=3 ttl=51 time=27.092 ms

64 bytes from 8.8.8.8: seq=4 ttl=51 time=27.008 ms

64 bytes from 8.8.8.8: seq=5 ttl=51 time=27.105 ms

64 bytes from 8.8.8.8: seq=6 ttl=51 time=27.007 ms

64 bytes from 8.8.8.8: seq=7 ttl=51 time=27.009 ms

64 bytes from 8.8.8.8: seq=8 ttl=51 time=27.008 ms

64 bytes from 8.8.8.8: seq=9 ttl=51 time=27.042 ms

64 bytes from 8.8.8.8: seq=10 ttl=51 time=26.824 ms

64 bytes from 8.8.8.8: seq=11 ttl=51 time=27.090 ms

64 bytes from 8.8.8.8: seq=12 ttl=51 time=26.846 ms

64 bytes from 8.8.8.8: seq=13 ttl=51 time=26.928 ms

64 bytes from 8.8.8.8: seq=14 ttl=51 time=26.877 ms

64 bytes from 8.8.8.8: seq=15 ttl=51 time=26.998 ms

64 bytes from 8.8.8.8: seq=16 ttl=51 time=26.898 ms

64 bytes from 8.8.8.8: seq=17 ttl=51 time=26.961 ms

64 bytes from 8.8.8.8: seq=18 ttl=51 time=26.933 ms

64 bytes from 8.8.8.8: seq=19 ttl=51 time=27.215 ms

64 bytes from 8.8.8.8: seq=20 ttl=51 time=27.014 ms

64 bytes from 8.8.8.8: seq=21 ttl=51 time=27.024 ms

64 bytes from 8.8.8.8: seq=22 ttl=51 time=26.989 ms

 

--- 8.8.8.8 ping statistics ---

23 packets transmitted, 20 packets received, 13% packet loss

round-trip min/avg/max = 26.824/26.993/27.215 ms

Trace
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets

1 192.168.1.254 0.671 ms 0.615 ms 0.612 ms

2 217.32.142.197 10.655 ms 10.738 ms 10.704 ms

3 217.32.142.222 11.907 ms 11.530 ms 11.515 ms

4 212.140.206.50 18.880 ms 18.409 ms 18.715 ms

5 31.55.165.45 16.932 ms 16.685 ms 17.258 ms

6 31.55.165.107 17.069 ms 16.842 ms 16.978 ms

7 109.159.250.48 18.780 ms 109.159.250.98 16.726 ms 109.159.250.90 16.596 ms

8 109.159.250.22 26.753 ms 109.159.250.38 25.434 ms 109.159.250.34 26.447 ms

9 109.159.254.34 25.941 ms 62.172.102.9 28.288 ms 109.159.254.34 26.796 ms

10 109.159.253.67 26.066 ms 24.941 ms 27.746 ms

11 72.14.234.65 26.621 ms 216.239.54.237 28.353 ms 216.239.54.215 25.677 ms

12 72.14.239.155 25.314 ms 74.125.37.117 25.747 ms 209.85.245.223 25.386 ms

Link to comment
Share on other sites

Mmm, some packet loss...

 

Could just be 8.8.8.8 I suppose. Have you checked on pingplotter to see if you're losing packets to a different server?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...