Camride, thank you!

Download or open Firefox. Download & install the Firebug plugin. You should see a little bug icon on the top right of the browser now. Please click that, and then navigate to the 'net' tab. Once there, enable logging as it asks you to do.

Now, please reload, or load up a CZ28 Thread. You should see a bunch of line items, with bars indicating how long each element took to load. It will likely take up a bit of space, you may need to scroll to see it all. You can drag the 'net' tab up from the bottom half of the browser, to make it take up the entire window. Then, if you could please take a screenshot, or a number of screenshots, to capture everything that it says in that 'net' tab. Then please post that into this thread for me, or you may email me if that's easier.

cheers,
robb

 

Well that's tiny: http://i110.photobucket.com/albums/n...8/PingTest.jpg CZ28 on the left, MBWorld on the right in case you don't have your IPs memorized.

 

Damn tiny pictures! http://i110.photobucket.com/albums/n...8/Firebug1.jpg http://i110.photobucket.com/albums/n...8/Firebug2.jpg

Of course it's broken car syndrome, it's not that slow right now. Next time I notice it being really slow though I'll fire this up and take some screen shots.

 

6% packet loss is a red flag, and a 15s page load is an even bigger red flag. I am not having the same experience, but I don't doubt your info one bit.

Can you let me know who your ISP is as well? I'm creating a critical ticket for our tech team right now with the info that you've supplied me. Thanks for your assistance!

cheers,
robb

 

We've got dual circuits here, a 50MB Time Warner circuit and a 20MB AT&T circuit. Unfortunately (for troubleshooting) they're load balanced so I can't tell you what circuit I'm going out. But bandwidth certainly isn't an issue on this end. I can do some traceroutes and see if I'm consistently going out one or the other though.

 

Understood re: your connection. Shouldn't matter anyway. Thanks muchly for your assistance.

 

No problem, let me know if there's anything else I can to do test or help out.

 

It's been awhile since I've done that stuff but I'll give it a shot when I get home from work tonight.

 

 

#2, use the command "ping -n 100 www.camaroz28.com", that will ping the server 100 times and give you a better idea of if there is any packet loss.

 

CZ28



MBWorld

 

I wonder if it's a Chrome thing? This morning at home I refreshed the page in Chrome and it took a solid 30 seconds. Once I noticed it was going slow I pulled up Firefox real quick and it loaded in under 5 seconds. I ran it a couple more times and no issues from Firefox. The next time I refreshed from Chrome it was faster, so maybe it's some missed packets/re-transmissions, not sure. But I've been doing CTRL+F5 all morning from work and I haven't gotten a page load above 4 seconds.

 

I hesitate to say that this is surely related, but apparently there were some issues ongoing in our internal network for a couple of days, though yesterday was the worst of it. There was a lot of technical mumbo jumbo emails sent out last evening, and overnight, indicating a whole whack of network changes taking place within our server farm.

I am cautiously optimistic that the work which was done, has alleviated the problems being experienced here by you folks.

I'll monitor this thread today, and would appreciate any more feedback positive, or negative that you guys can offer based on your browsing experience. I have never heard of Chrome being slower than firefox, but I'm typically a Safari user myself, and haven't noted any page loads longer than 4-5s ever. If in fact it's a Chrome specific issue, that gives me some more info to pass to the tech team, that may prove helpful.

cheers,
robb

 

A little more detail on the Chrome side (since I don't have the debugging tool to give me hard info). When I just went and refreshed the Lounge main page a minute ago it took 18 seconds before the page even attempted to refresh. At the bottom it just said "waiting for www.camaroz28.com". Once the page actually started to refresh (went blank) it went quickly, it was the 18 seconds waiting for a response that seems to kill it. I don't seem to get that in Firefox, at least not yet. But the actual refresh time seems to be fast even in Chrome, it's just that initial waiting that makes it take so long.

 

I just cracked open my Chrome, and loaded the 'lounge' in under 4 seconds. This stuff is way over my head, but you can be sure I will pass along all of this info to our tech guys to look into. I really appreciate your guys' help, and hope that we can figure out the issue ASAP.