Skip to main content

Ping spikes on Mac OS X

Problem: After (I think) an update my Mac began to show a strange pattern of network latency: A ping to my router would show a string of 1ms trip times punctuated periodically by a cluster of 400-1000ms latencies. I first realized something was wrong when I was playing counter strike and my ping would go crazy - on a server I frequent my typical ping used to be 20ms, but now it would register as 190ms, 400ms and so on. I could verify this was not a internet provider issue by pinging my router from a different computer and getting a steady string of 1ms latencies.

The solution was remarkably hard to find even though it seemed to be a common problem faced mostly by Mac users. A common response was to turn off anti-virus software, and I knew this was not the correct answer.

Solution: From the thread here (look for the answer by "eyepaq") it seems to be a bad setting or combination of settings in network preferences which can be reset by deleting the file "/Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist" and rebooting.

I was a little surprised at how happy I was that I could play CS:S again - not that I play so much, it was just such an annoying problem.

UPDATE: One of the other symptoms of this problem is garbled audio and stuttering video on google hangout sessions ...
Labels:

Comments

Post a Comment

Popular posts from this blog

A note on Python's __exit__() and errors

Python's context managers are a very neat way of handling code that needs a teardown once you are done. Python objects have do have a destructor method ( __del__ ) called right before the last instance of the object is about to be destroyed. You can do a teardown there. However there is a lot of fine print to the __del__ method. A cleaner way of doing tear-downs is through Python's context manager , manifested as the with keyword. class CrushMe: def __init__(self): self.f = open('test.txt', 'w') def foo(self, a, b): self.f.write(str(a - b)) def __enter__(self): return self def __exit__(self, exc_type, exc_val, exc_tb): self.f.close() return True with CrushMe() as c: c.foo(2, 3) One thing that is important, and that got me just now, is error handling. I made the mistake of ignoring all those 'junk' arguments ( exc_type, exc_val, exc_tb ). I just skimmed the docs and what popped out is that you need to return True or...
Post a Comment
Read more

Store numpy arrays in sqlite

Use numpy.getbuffer (or sqlite3.Binary ) in combination with numpy.frombuffer to lug numpy data in and out of the sqlite3 database: import sqlite3, numpy r1d = numpy.random.randn(10) con = sqlite3.connect(':memory:') con.execute("CREATE TABLE eye(id INTEGER PRIMARY KEY, desc TEXT, data BLOB)") con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", sqlite3.Binary(r1d))) con.execute("INSERT INTO eye(desc,data) VALUES(?,?)", ("1d", numpy.getbuffer(r1d))) res = con.execute("SELECT * FROM eye").fetchall() con.close() #res -> #[(1, u'1d', <read-write buffer ptr 0x10371b220, size 80 at 0x10371b1e0>), # (2, u'1d', <read-write buffer ptr 0x10371b190, size 80 at 0x10371b150>)] print r1d - numpy.frombuffer(res[0][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] print r1d - numpy.frombuffer(res[1][2]) #->[ 0. 0. 0. 0. 0. 0. 0. 0. 0. 0.] Note that for work where data ty...
Post a Comment
Read more