Ping times!
We dropped our bandwidth from 16mbit to 1.5mbit today. I also cleared Packeteer’s class tree and recreated it from scripts.
Packeteer is so fast.
It’s insane. I never thought I’d say that. With all the improvements they’ve made over the last year, and the fact that we have about 1/1000th the network load we did a week ago it only makes sense that it would be zippy.
Here are some ping stats from my house (qwest DSL):
- restek main server (66.165.0.24): 84ms
- campus DNS server (140.160.242.13): 90ms
- office machine (140.160.214.91): 89ms
- yahoo.com (216.109.127.28): 336ms
- fibercloud (216.57.204.2): 83ms
Those are all averages, and I did about 5 pings to each.
Summary:
- We’re slightly beating the academic network.
- We’re less that 5ms slower that fibercloud, meaning Packeteer is adding way less lag to the connection.
We must protect Packeteer from the evil flow monsters on campus next fall. We must have 2 firewalls.