Q: os x 10.10.3 installed and wifi slowed down

Possibly if this bug suddenly starts to effect a lot of people and/or people within Apple, then they might put out an emergency update, otherwise I'd say at the very best something might get addressed in 10.10.4 which will be what like 3 months from now.

I'm tempted to do a full erase and reinstall and manually transfer my files/apps over to the fresh install but after what the dude above said about buying a brand new MBP to only then have the bug rear its ugly head again, I'm not sure whether to even bother doing it anymore.

I am having the exact same issue.  I normally get 125+ mbps down but right now I am running at about 2mbps, occasionally 15mbps.

Getting right up next to my Airport Extreme or the Comcast wifi router they provided hardly increases the speed.  Sometimes when I restart my computer I can get my full download speed for my first 1-2 speed tests and then it drops right back down to the 2mbps.

I called Comcast and had them check my connection and all was good.  Wired I can get my full download speed.

Things worked fine for me until I did the 10.10.3 update.

wifiguru wrote:

 

Supreem,

Your data almost certainly indicates that some process or some app is consuming data in the background on your original account. I would start killing processes one by one and check if the speed restores.

I cannot see how that theory can be possible, as my fix doesn't change anything that's running in the background or otherwise.

The fix in which I have exemplified simply involves logging out of my main user acccount and logging Into a new user account I created then logging back out of that and back into my original account. In terms of what's running or not running; not a single aspect changes.

Exactly, once you log out and log back in, some app/process is being terminated. But over time when this app/process gets going again, its consuming bandwidth. What does Activity Monitor ( under Network tab) show you ? Do you see some process constantly eating CPU/bandwidth ?

wifiguru wrote:

 

Exactly, once you log out and log back in, some app/process is being terminated. But over time when this app/process gets going again, its consuming bandwidth. What does Activity Monitor ( under Network tab) show you ? Do you see some process constantly eating CPU/bandwidth ?

Whatever is causing it, does not 'eat up the bandwidth again over time' from using the laptop, it's either super slow or if I do the fix it is then constantly fast again i.e. it only goes back to being slow when I either shutdown and boot up again or when I put it to sleep for a while. And also the issue exists in any user account created, it's all determined by which ever user account is logged into initially, the fist account I initially log into is super slow, then when I log out and into another user that user is fast, then I log back into my other user account and that is also fast.

What I don't understand from your theory is, how can bandwidth be consumed just on my laptop and not on any other devices? Meaning that I can do a speed test side by side (simultaneously) with my MBP and my Dads MBP or my brothers MBP or the numerous iPads and iPhones we have here and I will get 2Mbps and very other device gets 40Mbps, surely if the bandwidth is being consumed then it would be consumed for every other device connecting to the same WiFi network, so all devices would get a share not just my MacBook gets nothing and all the other devices get full speed connection.

It's a bug that's come about from updating to 10.10.3, that's what is factual about this. The update is causing a major bottleneck to my WiFi on initial login.

P.S. I checked the Activity Monitor Network Tab but nothing is rigorously consuming the bandwidth

Also I mentioned before this issue only happens on my home WiFi network, if I connect to someone else WiFi there's no issues at all, so if something was consuming my bandwidth surely it would do the same on someone else WiFi network. Plus it only happens with my laptop, whilst everyone else on my home network has no issues at all.

Anyway it's so confusing that I honestly don't know what to think haha, thanks for the tips on Activity Monitor though mate.

Pinged my Router:

PING 192.168.3.1 (192.168.3.1): 56 data bytes

64 bytes from 192.168.3.1: icmp_seq=0 ttl=64 time=5.923 ms

64 bytes from 192.168.3.1: icmp_seq=1 ttl=64 time=2.723 ms

64 bytes from 192.168.3.1: icmp_seq=2 ttl=64 time=3.971 ms

64 bytes from 192.168.3.1: icmp_seq=3 ttl=64 time=5.757 ms

64 bytes from 192.168.3.1: icmp_seq=4 ttl=64 time=7.325 ms

64 bytes from 192.168.3.1: icmp_seq=5 ttl=64 time=1.501 ms

64 bytes from 192.168.3.1: icmp_seq=6 ttl=64 time=1.207 ms

64 bytes from 192.168.3.1: icmp_seq=7 ttl=64 time=2.179 ms

64 bytes from 192.168.3.1: icmp_seq=8 ttl=64 time=5.752 ms

64 bytes from 192.168.3.1: icmp_seq=9 ttl=64 time=6.358 ms

64 bytes from 192.168.3.1: icmp_seq=10 ttl=64 time=11.455 ms

Pinged a webpage based in my country:

PING orf.at (194.232.104.140): 56 data bytes

64 bytes from 194.232.104.140: icmp_seq=0 ttl=54 time=95.225 ms

64 bytes from 194.232.104.140: icmp_seq=1 ttl=54 time=157.336 ms

64 bytes from 194.232.104.140: icmp_seq=2 ttl=54 time=650.950 ms

64 bytes from 194.232.104.140: icmp_seq=3 ttl=54 time=94.488 ms

64 bytes from 194.232.104.140: icmp_seq=4 ttl=54 time=82.042 ms

64 bytes from 194.232.104.140: icmp_seq=5 ttl=54 time=120.636 ms

64 bytes from 194.232.104.140: icmp_seq=6 ttl=54 time=54.551 ms

64 bytes from 194.232.104.140: icmp_seq=7 ttl=54 time=158.925 ms

64 bytes from 194.232.104.140: icmp_seq=8 ttl=54 time=141.690 ms

64 bytes from 194.232.104.140: icmp_seq=9 ttl=54 time=121.706 ms

64 bytes from 194.232.104.140: icmp_seq=10 ttl=54 time=188.929 ms

64 bytes from 194.232.104.140: icmp_seq=11 ttl=54 time=123.764 ms

64 bytes from 194.232.104.140: icmp_seq=12 ttl=54 time=146.263 ms

64 bytes from 194.232.104.140: icmp_seq=13 ttl=54 time=193.536 ms

64 bytes from 194.232.104.140: icmp_seq=14 ttl=54 time=142.250 ms

64 bytes from 194.232.104.140: icmp_seq=15 ttl=54 time=190.580 ms

64 bytes from 194.232.104.140: icmp_seq=16 ttl=54 time=114.367 ms

64 bytes from 194.232.104.140: icmp_seq=17 ttl=54 time=142.042 ms

64 bytes from 194.232.104.140: icmp_seq=18 ttl=54 time=135.729 ms

64 bytes from 194.232.104.140: icmp_seq=19 ttl=54 time=136.004 ms

64 bytes from 194.232.104.140: icmp_seq=20 ttl=54 time=27.243 ms

^C

--- orf.at ping statistics ---

21 packets transmitted, 21 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 27.243/153.250/650.950/118.528 ms

Pinged apple.com:

PING apple.com (17.142.160.59): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

Request timeout for icmp_seq 4

Request timeout for icmp_seq 5

Request timeout for icmp_seq 6

Request timeout for icmp_seq 7

Request timeout for icmp_seq 8

Request timeout for icmp_seq 9

Request timeout for icmp_seq 10

Request timeout for icmp_seq 11

Request timeout for icmp_seq 12

Request timeout for icmp_seq 13

Request timeout for icmp_seq 14

Request timeout for icmp_seq 15

Request timeout for icmp_seq 16

Request timeout for icmp_seq 17

Request timeout for icmp_seq 18

Request timeout for icmp_seq 19

Request timeout for icmp_seq 20

^C

--- apple.com ping statistics ---

22 packets transmitted, 0 packets received, 100.0% packet loss

And another webpage not based in my country:

PING theverge.com (216.146.46.11): 56 data bytes

64 bytes from 216.146.46.11: icmp_seq=0 ttl=51 time=135.904 ms

64 bytes from 216.146.46.11: icmp_seq=1 ttl=51 time=137.869 ms

64 bytes from 216.146.46.11: icmp_seq=2 ttl=51 time=141.581 ms

64 bytes from 216.146.46.11: icmp_seq=3 ttl=51 time=129.641 ms

64 bytes from 216.146.46.11: icmp_seq=4 ttl=51 time=129.285 ms

64 bytes from 216.146.46.11: icmp_seq=5 ttl=51 time=411.204 ms

64 bytes from 216.146.46.11: icmp_seq=6 ttl=51 time=126.922 ms

64 bytes from 216.146.46.11: icmp_seq=7 ttl=51 time=162.667 ms

64 bytes from 216.146.46.11: icmp_seq=8 ttl=51 time=156.219 ms

64 bytes from 216.146.46.11: icmp_seq=9 ttl=51 time=133.263 ms

64 bytes from 216.146.46.11: icmp_seq=10 ttl=51 time=127.649 ms

64 bytes from 216.146.46.11: icmp_seq=11 ttl=51 time=135.708 ms

64 bytes from 216.146.46.11: icmp_seq=12 ttl=51 time=126.154 ms

64 bytes from 216.146.46.11: icmp_seq=13 ttl=51 time=128.119 ms

64 bytes from 216.146.46.11: icmp_seq=14 ttl=51 time=130.305 ms

64 bytes from 216.146.46.11: icmp_seq=15 ttl=51 time=125.278 ms

64 bytes from 216.146.46.11: icmp_seq=16 ttl=51 time=134.422 ms

64 bytes from 216.146.46.11: icmp_seq=17 ttl=51 time=133.060 ms

64 bytes from 216.146.46.11: icmp_seq=18 ttl=51 time=136.027 ms

64 bytes from 216.146.46.11: icmp_seq=19 ttl=51 time=191.597 ms

64 bytes from 216.146.46.11: icmp_seq=20 ttl=51 time=454.852 ms

^C

--- theverge.com ping statistics ---

21 packets transmitted, 21 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 125.278/166.082/454.852/88.158 ms

Even pinged discussions.apple.com:

ping discussions.apple.com

PING e4233.a.akamaiedge.net (2.17.21.54): 56 data bytes

64 bytes from 2.17.21.54: icmp_seq=0 ttl=55 time=34.115 ms

64 bytes from 2.17.21.54: icmp_seq=1 ttl=55 time=36.033 ms

64 bytes from 2.17.21.54: icmp_seq=2 ttl=55 time=37.012 ms

64 bytes from 2.17.21.54: icmp_seq=3 ttl=55 time=35.573 ms

64 bytes from 2.17.21.54: icmp_seq=4 ttl=55 time=36.825 ms

64 bytes from 2.17.21.54: icmp_seq=5 ttl=55 time=43.125 ms

64 bytes from 2.17.21.54: icmp_seq=6 ttl=55 time=40.213 ms

64 bytes from 2.17.21.54: icmp_seq=7 ttl=55 time=44.997 ms

64 bytes from 2.17.21.54: icmp_seq=8 ttl=55 time=420.770 ms

64 bytes from 2.17.21.54: icmp_seq=9 ttl=55 time=130.464 ms

64 bytes from 2.17.21.54: icmp_seq=10 ttl=55 time=511.271 ms

64 bytes from 2.17.21.54: icmp_seq=11 ttl=55 time=56.532 ms

64 bytes from 2.17.21.54: icmp_seq=12 ttl=55 time=153.613 ms

64 bytes from 2.17.21.54: icmp_seq=13 ttl=55 time=35.311 ms

64 bytes from 2.17.21.54: icmp_seq=14 ttl=55 time=37.041 ms

64 bytes from 2.17.21.54: icmp_seq=15 ttl=55 time=45.864 ms

64 bytes from 2.17.21.54: icmp_seq=16 ttl=55 time=35.575 ms

64 bytes from 2.17.21.54: icmp_seq=17 ttl=55 time=36.202 ms

64 bytes from 2.17.21.54: icmp_seq=18 ttl=55 time=36.043 ms

64 bytes from 2.17.21.54: icmp_seq=19 ttl=55 time=36.416 ms

64 bytes from 2.17.21.54: icmp_seq=20 ttl=55 time=35.876 ms

64 bytes from 2.17.21.54: icmp_seq=21 ttl=55 time=38.570 ms

64 bytes from 2.17.21.54: icmp_seq=22 ttl=55 time=34.717 ms

Request timeout for icmp_seq 23

64 bytes from 2.17.21.54: icmp_seq=24 ttl=55 time=355.039 ms

64 bytes from 2.17.21.54: icmp_seq=25 ttl=55 time=579.265 ms

64 bytes from 2.17.21.54: icmp_seq=26 ttl=55 time=44.774 ms

64 bytes from 2.17.21.54: icmp_seq=27 ttl=55 time=42.365 ms

64 bytes from 2.17.21.54: icmp_seq=28 ttl=55 time=35.696 ms

64 bytes from 2.17.21.54: icmp_seq=29 ttl=55 time=36.579 ms

64 bytes from 2.17.21.54: icmp_seq=30 ttl=55 time=180.299 ms

64 bytes from 2.17.21.54: icmp_seq=31 ttl=55 time=35.779 ms

64 bytes from 2.17.21.54: icmp_seq=32 ttl=55 time=36.597 ms

64 bytes from 2.17.21.54: icmp_seq=33 ttl=55 time=39.839 ms

64 bytes from 2.17.21.54: icmp_seq=34 ttl=55 time=35.459 ms

64 bytes from 2.17.21.54: icmp_seq=35 ttl=55 time=44.102 ms

64 bytes from 2.17.21.54: icmp_seq=36 ttl=55 time=616.047 ms

Request timeout for icmp_seq 37

Request timeout for icmp_seq 38

64 bytes from 2.17.21.54: icmp_seq=39 ttl=55 time=98.959 ms

64 bytes from 2.17.21.54: icmp_seq=40 ttl=55 time=287.056 ms

64 bytes from 2.17.21.54: icmp_seq=41 ttl=55 time=34.338 ms

64 bytes from 2.17.21.54: icmp_seq=42 ttl=55 time=35.637 ms

64 bytes from 2.17.21.54: icmp_seq=43 ttl=55 time=46.196 ms

64 bytes from 2.17.21.54: icmp_seq=44 ttl=55 time=278.167 ms

64 bytes from 2.17.21.54: icmp_seq=45 ttl=55 time=35.642 ms

64 bytes from 2.17.21.54: icmp_seq=46 ttl=55 time=36.336 ms

64 bytes from 2.17.21.54: icmp_seq=47 ttl=55 time=43.693 ms

64 bytes from 2.17.21.54: icmp_seq=48 ttl=55 time=44.374 ms

64 bytes from 2.17.21.54: icmp_seq=49 ttl=55 time=38.972 ms

64 bytes from 2.17.21.54: icmp_seq=50 ttl=55 time=33.161 ms

^C

--- e4233.a.akamaiedge.net ping statistics ---

51 packets transmitted, 48 packets received, 5.9% packet loss

round-trip min/avg/max/stddev = 33.161/105.136/616.047/147.777 ms

Same problem with wifi speed for me, MBPr late 2013, I've done some test and here are result, wifi speed is the slowest on 5GHz band, when I switch to 2,4GHz band, speed is better, turn off bluetooth has positive efect to wifi speed. When I'm conneted PC via thunderbolt 2 -> Ethernet adapter, the speed is more then 6x slower with turn on bluetooth then with bluetooth is turned off!!!

I've not found any solotion for this moment.

BR

Have you tried a fresh re-install of the OS? I'm sheepishly waiting for someone to do that haha and see if it's a fix or not, I may have to be the guinea pig!

No, for this moment I try to find reason, when the problem is, and now, I will try to find solution, fresh re-install is the last option for me!

I would try it, but as my connection is that horribly slow, it would need about 20+ hours to download

Yeah what you'd need to do is go use someone else's WiFi connection (family or friend's house), as your WiFi speeds there should be unaffected by his bug.

Unless something pops up on here fix wise, then in a week or so from now I'll erase my HD and do a fresh install of OS X. If that doesn't fix it then I dunno what to do... move house??

iW@nt,

your pings to the LAN are almost perfect. Your WAN side latencies are pretty high. Wi-Fi looks good, i bet you did an internal file transfer or something it would work without issues. Somethings going on behind the router - does your ISP throttle speeds ( assuming you download 10.10.3 or have Photos uploading in the background ? )

But even accessing my router preferences takes as long as accessing a normal website (about 15-30 seconds depending on website).

Furthermore, my iPhone, iPad and PS4 download and upload at full speed and when I'm connected to a different WiFi or a hotspot with my laptop, I'm getting smooth up/down and ping latency, too.

Download at the time is about 1 Mbit as opposed to a normal rate of 14 Mbit on my MBP.