yeah... we know.. just giving zoeb a hard time

 

What did Zoeb Do?

 

There's a noticeable improvement:

10/06/04 11:38:48 Fast traceroute i-club.com
Trace i-club.com (64.119.173.9) ...
1 10.184.32.1 9ms 14ms 21ms TTL: 0 (No rDNS)
2 12.244.118.177 59ms 16ms 23ms TTL: 0 (No rDNS)
3 12.127.32.89 11ms 22ms 25ms TTL: 0 (No rDNS)
4 12.123.13.177 20ms 25ms 27ms TTL: 0 (tbr2-p013701.sffca.ip.att.net probable bogus rDNS: No DNS)
5 12.122.12.134 48ms 35ms 36ms TTL: 0 (gbr3-p10.dvmco.ip.att.net probable bogus rDNS: No DNS)
6 12.122.5.18 54ms 36ms 34ms TTL: 0 (gbr1-p100.dvmco.ip.att.net probable bogus rDNS: No DNS)
7 12.123.36.137 63ms 37ms 38ms TTL: 0 (gar2-p360.dvmco.ip.att.net probable bogus rDNS: No DNS)
8 12.124.158.58 73ms 41ms 42ms TTL: 0 (att-46.den.internap.ip.att.net probable bogus rDNS: No DNS)
9 216.52.40.78 74ms 42ms 47ms TTL: 0 (border9.ge4-1-bbnet2.den.pnap.net probable bogus rDNS: No DNS)
10 63.251.181.210 99ms 46ms 49ms TTL: 0 (data393-3.border9.den.pnap.net probable bogus rDNS: No DNS)
11 208.42.224.5 108ms 60ms 60ms TTL: 0 (core-a.v21.ge-2-7.Internap-2.edge2.data393.net probable bogus rDNS: No DNS)
12 208.42.224.34 49ms 65ms 53ms TTL: 0 (rtr-dc-dist-a.v14.colo.data393.net probable bogus rDNS: No DNS)
13 64.119.173.9 49ms 70ms 56ms TTL: 51 (No rDNS)

--
0==WW==0
"…axles of evil…" - george w. bush

 

I have no idea what I'm looking at. But I will take your word for it.

-Chris

 

+1

 

The access time in milliseconds was significantly longer recently. I don't exactly know what Alex did to correct it or what exactly was the problem. Zoeb?

--
0==WW==0
"…axles of evil…" - george w. bush

 

Why would he have to mess with the vB database if the actual internet traffic was the problem?

<--knows nothing

 

Beats me. I probably know less than you. I win!

--
0==WW==0
"…axles of evil…" - george w. bush

 

No wonder your seeing latency, your ISP AT&T. ;D

 

Here is my traceroute, makes a little more sense to some of you maybe. =x


Packets Pings
Hostname %Loss Rcv Snt Last Best Avg Worst
1. blueia.slakin.net 0% 264 264 0 0 0 1
2. netblock-66-159-225-1.dslextreme.com 0% 264 264 6 5 25 130
3. f0-1-1.cr1.sjc1.dslextreme.com 0% 264 264 38 6 39 726
4. ge-8-0-132.ipcolo2.SanJose1.Level3.net 1% 263 264 44 6 28 140
5. ge-1-1-0-56.bbr2.SanJose1.Level3.net 1% 263 264 7 7 28 107
6. so-3-0-0.mp2.Denver1.Level3.net 1% 262 263 40 39 59 144
7. so-6-0.hsa2.Denver1.Level3.net 0% 263 263 40 39 58 172
8. unknown.Level3.net 0% 263 263 50 36 55 147
9. border9.ge4-1-bbnet2.den.pnap.net 1% 262 263 37 36 63 302
10. data393-3.border9.den.pnap.net 1% 261 263 52 36 56 159
11. core-a.v21.ge-2-7.Internap-2.edge2.data393.net 1% 261 263 70 50 77 267
12. rtr-dc-dist-b.v14.colo.data393.net 0% 263 263 92 50 71 166
13. 64.119.173.9 1% 262 263 56 50 72 181

 

Now that I'm at home it seems to be fast again!!! (At least for now )

However, when I click on a new thread (they're bold) and then go back, they stay bold !?!?!?! I don't get it. Did something change or am I confused? when I used to click on something it would then become unbold just like all the others I've read (or are simply to old, or weren't posted since I last visited.)

Is anyone else experiencing this too, or am I just teh stupid?

 

Yes, this is something that's changed. Might have something to do with the way cookies are updated. I used to enjoy using browser 'back' button and the thread list would already be updated for viewed threads.

--
0==WW==0
"…axles of evil…" - george w. bush

 

Showing a ping table doesn't show a whole lot in terms of server performance, it only shows the switches in between.

This little thing shows how fast the server is working "Page generated in 0.28556094 seconds (87.97% PHP - 12.03% MySQL)" Still a tad pokey, but probably not on the fastest server around.

What gzip level are you guys using? I found 2 worked best when I was using vbulletin. I changed to PNphpBB after getting sick of paying vbulletin year after year, and them getting more and more expensive year after year(as if paying to co-locate a server isn't expensive enough)

 

I call the big one bitey.

-Chris