Forum Settings
       
Reply To Thread

Moving, Unfortunate Internet Speed DecreaseFollow

#1 Apr 07 2014 at 10:50 AM Rating: Good
So I'm moving to a new location tomorrow and after talking to my ISP, CenturyLink, today about moving my services, I'm being told I have no choice but to drop from 40Mbps Down / 20Mbps Up (Which I reliably got), to 1.5Mbps down, 768Kbps up. At least my bill will go down...

My question to the community is -- Does anyone run XIV on this kind of connection? What's it like? Do you have issues with loading? I can't imagine latency is going to be an issue, unless it's so slow because the copper is terrible.
#2 Apr 07 2014 at 11:03 AM Rating: Excellent
Avatar
*
144 posts
.......Ouch.

I once tried playing from work on a T1 line at 1.5Mbps down, 1.5 up. It seemed to run just fine, so hopefully it'll work out alright for you. Not the same, true, at least when downloading updates, but while you are playing, it should be sufficient. Good luck with that connection! And good luck with moving! I've done that too many times.
____________________________
Primary World: Hyperion
Free Company: Jormungandr
Legacy Member
Main Character: Fialas Dawnren: Level 60 BRD/AST/MNK/DoL, Level 16-50 On Everything Else
#3 Apr 07 2014 at 11:08 AM Rating: Excellent
I do, actually. My DSL connection with AT&T is 3.0 mbps down and 0.5 up.

The QoS is great, though, and that's what really makes a difference. I get 10 ms pings to Google and the connection never drops.

Now, if someone is trying to stream at the same time you're playing, it's can be pretty awful. If you have others in your household trying to watch Netflix, you're going to hate it. When XIV is the sole thing going, though, you're gonna play just as good as someone on super fat pipes. XIV's data architecture is like XI's was - it sips data rather than sucks it.
#4 Apr 07 2014 at 1:51 PM Rating: Excellent
***
2,550 posts
Catwho wrote:
super fat pipes.


Smiley: clap
#5 Apr 07 2014 at 1:54 PM Rating: Good
Catwho wrote:
Now, if someone is trying to stream at the same time you're playing, it's can be pretty awful.


Fortunately that won't be a problem. My living situation is going to be shared with the rents (gotta love when life happens like that, I'm getting too old to move back in with them), and they have a 1.5mb pipe of their own. Considering the limited bandwidth I elected to just install my line as a second line, so they'll never be impacting my bandwidth.

Unless, of course, it's a situation where the copper literally only supports 1.5mbps bandwidth, and irregardless of what they do they'll impact my line. Then I'm screwed.

For ping, right now I'm getting between 30-40ms ping. They're out in the boons. I'm hoping it doesn't go up much.

Edited, Apr 7th 2014 3:55pm by darexius2010
#6 Apr 07 2014 at 7:17 PM Rating: Excellent
***
3,441 posts
I play on 3Mbps Down and .75Mbps up and I do fine.

The game doesn't use anywhere near the 3Mbps; I can game in FFXIV even in a dungeon or FATEs while someone else on the LAN is on WoW at the same time and there's no noticeable latency.

In fact, there've been times that someone was watching Youtube (though it was full Audio or B&W movies) at the same time, and the latency was only mild with occasional bursts, usually about 200-300ms while they were on Youtube.

Outside of that, I get 40ms pings to Google.

Most MMORPGs do not need huge bandwidth; they need fast pings. As long as you're sub-100ms to Google, you will be fine on any sort of broadband.
#7 Apr 08 2014 at 3:53 PM Rating: Good
Aaaaand the results are in:

Robs-Mac:~ robcrist$ ping google.com 
PING google.com (74.125.224.206): 56 data bytes 
64 bytes from 74.125.224.206: icmp_seq=0 ttl=57 time=524.744 ms 
64 bytes from 74.125.224.206: icmp_seq=1 ttl=57 time=542.385 ms 
64 bytes from 74.125.224.206: icmp_seq=2 ttl=57 time=365.221 ms 
64 bytes from 74.125.224.206: icmp_seq=3 ttl=57 time=395.693 ms 
64 bytes from 74.125.224.206: icmp_seq=4 ttl=57 time=439.088 ms 
64 bytes from 74.125.224.206: icmp_seq=5 ttl=57 time=551.106 ms 
64 bytes from 74.125.224.206: icmp_seq=6 ttl=57 time=439.747 ms 
64 bytes from 74.125.224.206: icmp_seq=7 ttl=57 time=467.996 ms 
64 bytes from 74.125.224.206: icmp_seq=8 ttl=57 time=529.633 ms 
64 bytes from 74.125.224.206: icmp_seq=9 ttl=57 time=529.865 ms 
64 bytes from 74.125.224.206: icmp_seq=10 ttl=57 time=391.831 ms 
64 bytes from 74.125.224.206: icmp_seq=11 ttl=57 time=482.434 ms 
64 bytes from 74.125.224.206: icmp_seq=12 ttl=57 time=550.372 ms 
^C 
--- google.com ping statistics --- 
13 packets transmitted, 13 packets received, 0.0% packet loss 
round-trip min/avg/max/stddev = 365.221/477.701/551.106/63.418 ms


Robs-Mac:~ robcrist$ traceroute google.com 
traceroute: Warning: google.com has multiple addresses; using 74.125.224.206 
traceroute to google.com (74.125.224.206), 64 hops max, 52 byte packets 
 1  192.168.0.1 (192.168.0.1)  2.825 ms  2.813 ms  2.684 ms 
 2  phnx-dsl-gw69.phnx.qwest.net (67.40.227.69)  629.676 ms  556.850 ms  557.020 ms 
 3  phnx-agw1.inet.qwest.net (75.160.238.33)  544.188 ms  451.056 ms  452.043 ms 
 4  los-edge-05.inet.qwest.net (67.14.22.106)  477.754 ms  55.153 ms  60.801 ms 
 5  65.113.16.38 (65.113.16.38)  70.364 ms  53.531 ms  53.063 ms 
 6  * * * 
 7  72.14.236.13 (72.14.236.13)  57.222 ms  55.668 ms  62.273 ms 
 8  lax02s02-in-f14.1e100.net (74.125.224.206)  56.775 ms  57.005 ms  59.790 ms 


That's interesting is that the requests directly to CenturyLink/Qwest during the hop are taking forever. Everything else is sound. Interesting.
#8 Apr 08 2014 at 4:09 PM Rating: Excellent
***
3,441 posts
I would definitely call your ISP.

600ms pings are wholly unacceptable for broadband unless you're on Satellite.

There is no reason why anything should be 600ms to Google, let alone the first hop in the Traceroute.
#9 Apr 08 2014 at 4:12 PM Rating: Excellent
That's what I'm going to do in the morning (still unloading the U-Haul, who knew I had so much stuff!). I have their in-home wiring insurance package so if anything is wrong they'll fix it at no cost to me other than the monthly $4 I pay. I've seen 100ms out of DSL. I've not seen upwards of 700ms, though. Even on satellite. Worst I've seen on satellite has been in the 400's
#10 Apr 13 2014 at 3:10 PM Rating: Good
Did some more diagnostics now that I'm moved in full-time. Turned out that everyone believes that those little boxes you plug into the wall between a regular phone and the wall are some kind of mythical recording device for the NSA. Plugged them in, this is what I got

Robs-Mac:~ robcrist$ traceroute google.com 
traceroute: Warning: google.com has multiple addresses; using 74.125.224.98 
traceroute to google.com (74.125.224.98), 64 hops max, 52 byte packets 
 1  192.168.0.1 (192.168.0.1)  2.982 ms  3.131 ms  2.699 ms 
 2  phnx-dsl-gw69.phnx.qwest.net (67.40.227.69)  154.940 ms  41.888 ms  42.126 ms 
 3  phnx-agw1.inet.qwest.net (75.160.238.33)  42.233 ms  41.664 ms  42.281 ms 
 4  los-edge-05.inet.qwest.net (67.14.22.106)  55.344 ms  52.265 ms  54.563 ms 
 5  65.113.16.38 (65.113.16.38)  54.109 ms  83.560 ms  54.053 ms 
 6  * 64.233.174.238 (64.233.174.238)  53.223 ms  54.944 ms 
 7  209.85.250.245 (209.85.250.245)  54.982 ms  53.651 ms  53.333 ms 
 8  lax02s19-in-f2.1e100.net (74.125.224.98)  53.007 ms  56.001 ms  53.286 ms
#11 Apr 13 2014 at 3:27 PM Rating: Good
***
3,441 posts
darexius2010 wrote:
Did some more diagnostics now that I'm moved in full-time. Turned out that everyone believes that those little boxes you plug into the wall between a regular phone and the wall are some kind of mythical recording device for the NSA. Plugged them in, this is what I got

Robs-Mac:~ robcrist$ traceroute google.com 
traceroute: Warning: google.com has multiple addresses; using 74.125.224.98 
traceroute to google.com (74.125.224.98), 64 hops max, 52 byte packets 
 1  192.168.0.1 (192.168.0.1)  2.982 ms  3.131 ms  2.699 ms 
 2  phnx-dsl-gw69.phnx.qwest.net (67.40.227.69)  154.940 ms  41.888 ms  42.126 ms 
 3  phnx-agw1.inet.qwest.net (75.160.238.33)  42.233 ms  41.664 ms  42.281 ms 
 4  los-edge-05.inet.qwest.net (67.14.22.106)  55.344 ms  52.265 ms  54.563 ms 
 5  65.113.16.38 (65.113.16.38)  54.109 ms  83.560 ms  54.053 ms 
 6  * 64.233.174.238 (64.233.174.238)  53.223 ms  54.944 ms 
 7  209.85.250.245 (209.85.250.245)  54.982 ms  53.651 ms  53.333 ms 
 8  lax02s19-in-f2.1e100.net (74.125.224.98)  53.007 ms  56.001 ms  53.286 ms


I see a 154ms spike in amongst all of those 50s...

You doing all of this at the same time of day, or different times of the day?

IMO, next time you get a chance (especially on a weekend), I'd do 50 pings to google at, say, 8AM, Noon, 4PM, and 8PM and see if they are all about the same.

Maybe high-traffic (Sat. Evening, etc), the whole ISP is bogging down because of the traffic, while early morning off-times are just fine?

EDIT: Come to think of it, I had that very problem with my ADSL for awhile last year. I'd get wild pings in the early-mid evening hours and then suddenly it'd go back to normal. I'd do 50 pings to google and I'd get 5-10 pings that were 70ms and then I'd get 5 that were 500+ and then 5 that were 70ms, etc. When I called and asked them, they checked their stuff and they said that I was on a congested line and they switched me to another one and I now get 30-40ms to Google on average.

Edited, Apr 13th 2014 5:29pm by Lyrailis
#12 Apr 13 2014 at 4:06 PM Rating: Good
I have a tech coming out to install a second line tomorrow, and he'll be going over the existing cabling. It is odd that periodically, after going so long, it'll spike to around 150ms all of a sudden. Don't get me wrong, it's only like 1 ping among many, and it's sure as sight better than 700+ that I was getting, but it's still something to look at.

It's a shame that I can only get 1.5Mbps out here, but 1.5 isn't actually all that bad... when you don't have 700+ ping.
#13 Apr 13 2014 at 6:14 PM Rating: Good
***
3,441 posts
darexius2010 wrote:
I have a tech coming out to install a second line tomorrow, and he'll be going over the existing cabling. It is odd that periodically, after going so long, it'll spike to around 150ms all of a sudden. Don't get me wrong, it's only like 1 ping among many, and it's sure as sight better than 700+ that I was getting, but it's still something to look at.

It's a shame that I can only get 1.5Mbps out here, but 1.5 isn't actually all that bad... when you don't have 700+ ping.


Ping spikes are usually congestion, though I suppose line quality/noise can also cause it too. Though to be honest, from past experience whenever line quality/noise on the line was involved, the problem was more disconnects and dropped packets altogether.

As for 1.5Mbps... 1.5Mbps is fine when the pings are good, the only bad thing is it takes forever to download anything large (even 3Mbps takes forever to download 1GB+), and some streaming you might need to pause every 10min or so to let the buffer catch up on some of the higher-quality video streaming. As for playing a game, especially if you're the only person on your LAN, 1.5Mbps will be plenty fine, except for some Peer-to-Peer games (like Warframe), you might have trouble hosting some of these games (again, Warframe... even my 3Mbps connection struggles with it).
Reply To Thread

Colors Smileys Quote OriginalQuote Checked Help

 

Recent Visitors: 201 All times are in CST
Anonymous Guests (201)