CSC Server Performance *** UPDATE: Problem Linked to Google Chrome

[DevilsTonic]

ADMIN EDIT: This only seems to be a problem with Google Chrome. For instructions on how to fix it, scroll down to post #25 or click here.


Ralph / Bob, I know that you guys have many more important things to worry about with your real jobs. I just want to put this out here as I'm sure many people are experiencing the same delays in performing the simplest of tasks on CSC. This only started after the site was moved to the new servers. I'm not sure if it's a hard coded speed/duplex setting on the new hardware or maybe latency with the database.

I'm seeing delays in server response when clicking to view a thread, reply to a thread or to create a new thread. It took over 20 seconds after clicking the "New Thread" button to create this thread, I got no response and clicked it several more times before I was directed to the new thread page.

I've also noticed that there are many double posts. I'm not sure if that is because people are moderating their own posts (doubtful) or because they post, the server response is too slow so they attempt to post again and end up with a duplicate.

In running a continuous ping to the server I'm seeing inconsistent response times ranging from 9ms-200ms. I know that you are doing this on your own time, and I thank you for all the time and effort you put into keeping CSC running. I just wanted to make you aware in case this is something you may want to look into....in your copious three seconds of spare time of course!

[Ricky]

Problem: server connected to cisco switch port that is set to negotiate at a specific speed, and the network card in the server is set to auto negotiate.

Solution: set server NIC to negotiate at the same speed that the switch port is set to

[TurboGizzmo]

Problem: server connected to cisco switch port that is set to negotiate at a specific speed, and the network card in the server is set to auto negotiate.

Solution: set server NIC to negotiate at the same speed that the switch port is set to

Ha! Thats the first thing the network engineer consultant said to me (personal network issues)....most of network issues he deals with is a speed/duplex/negotiation issue.

PS Editing this post took 664ms for editpost.php to load

[Vellos]

For me when the page lags it will not load even if I try waiting for it. I have to keep trying and 1 out of 10 times it will instantly load.

[CaptGoodvibes]

60 percent of the time it works everytime

http://www.youtube.com/watch?v=zLq2-uZd5LY

[grim]

60 percent of the time it works everytime

http://www.youtube.com/watch?v=zLq2-uZd5LY

Where is the cookie? and i didnt get the invite to the pants party!

[rforsythe]

Problem: server connected to cisco switch port that is set to negotiate at a specific speed, and the network card in the server is set to auto negotiate.

Solution: set server NIC to negotiate at the same speed that the switch port is set to

Negative. Server is connected to a gigabit switch and everything is negotiated properly, and in any event the virtual machine running the web server talks to the VM running the database through a virtual switch where duplex doesn't really exist. That doesn't affect the ISP link however.

Folks I know it's annoying, and I will get it resolved as soon as I can. We are on a better server, but the ISP not so much as that got changed as well. The dupe posts are probably from people clicking submit multiple times waiting for reloads, though oddly enough I don't see these issues myself when I'm remote.

[t_jolt]

Ralph i know you've probably already looked, but could it be blocking on the Database? or disk queues? I know those disks are way faster then the old ones you were using, but maybe its a thought? or could their be proc contention with the vm's?

Tyrel

[Zach929rr]

I have experienced no problems at all.

[King Nothing]

waaaaaaaaaaaaaa It takes like a second for the threads to load. waaaaaaaaaaaa

people will bitch about anything.

[Sean]

I have experienced no problems at all.

That's because you're mentally slow. Your thought process and the servers are now in sync.

[Joe]

Since I don't understand any of this, but I'm very grateful for them...

[DevilsTonic]

waaaaaaaaaaaaaa It takes like a second for the threads to load. waaaaaaaaaaaa

people will bitch about anything.

No bitching here, just making a site comment.

[~Barn~]

I have experienced no problems at all.

+1

[Ricky]

Negative. Server is connected to a gigabit switch and everything is negotiated properly, and in any event the virtual machine running the web server talks to the VM running the database through a virtual switch where duplex doesn't really exist. That doesn't affect the ISP link however.

Folks I know it's annoying, and I will get it resolved as soon as I can. We are on a better server, but the ISP not so much as that got changed as well. The dupe posts are probably from people clicking submit multiple times waiting for reloads, though oddly enough I don't see these issues myself when I'm remote.

Strange... This is identical to issues I've seen on other web servers that had to do with port negotiation. But yeah, if it's virtual, that makes it a different ballgame. Some people notice it, some don't. Jitter is massive when pinging the server. It was never this way before the switch. It's so bad for me, that each time I click, I usually have to click 5-10 more times for the page to load. Otherwise, it times out completely.

waaaaaaaaaaaaaa It takes like a second for the threads to load. waaaaaaaaaaaa

people will bitch about anything.

And yet, here you are bitching about people bitching about something. Thanks for proving your own point. Holy fucking hypocrisy.

[gtn]

I haven't experienced any of the issues discussed above.

I just ran a set of 100 pings, and the hi/avg/lo were 129/92/87. No packets were lost.

Seems more like a peering issue with the ISP.

I have Comcast for an ISP at home. Sprint and Verizon at work. Though I haven't run the ping test from work, I do occasionally sneak a peak at CSC from there and haven't had any issues since the move.

[LivingPools]

No problems here, and I really appreciate the software upgrade to 'New Posts' functionality!

[DevilsTonic]

You may be onto something Ralph. Since you mentioned the browsers I started testing it in various scenarios. It just seems to be Chrome both in OSX and in Windows. I'm connecting to the site with Safari right now and I've tested with IE and Firefox and I haven't experienced the same delays. At least I can get my fix. That's all that matters! Thanks Ralph.

[rforsythe]

This seems to be a caching issue with Chrome specifically, and not unheard of on the Internet. My guess is Chrome is trying to remember some old location for files, and it can't find it there so it all but stops. For those of you using it, please clear all cache and page history out of it and see what happens.

[Tylar]

This seems to be a caching issue with Chrome specifically, and not unheard of on the Internet. My guess is Chrome is trying to remember some old location for files, and it can't find it there so it all but stops. For those of you using it, please clear all cache and page history out of it and see what happens.

Done that a few times, no joy.

I'm just sticking to Safari when I need to read about drama....because I just have to have it.

[rforsythe]

Done that a few times, no joy.

I'm just sticking to Safari when I need to read about drama....because I just have to have it.

Yeah, according to one article, clicking delete doesn't actually do it - you have to go manually nuke the files. Google it if you care that much.

[cptschlongenheimer]

This seems to be a caching issue with Chrome specifically, and not unheard of on the Internet. My guess is Chrome is trying to remember some old location for files, and it can't find it there so it all but stops. For those of you using it, please clear all cache and page history out of it and see what happens.

Did these. Helped at first but after closing a few threads and reopening I started seeing timeouts again. Read a tech bulletin that said DNS pre-fetching in chrome may be the issue. Trying now with that turned off. So far, all is good?

[Tylar]

Yeah, according to one article, clicking delete doesn't actually do it - you have to go manually nuke the files. Google it if you care that much.

Google is starting to act like the collective...

Did these. Helped at first but after closing a few threads and reopening I started seeing timeouts again. Read a tech bulletin that said DNS pre-fetching in chrome may be the issue. Trying now with that turned off. So far, all is good?

I'll try this. Two browsers for the single task of avoiding work is unacceptable.

[cptschlongenheimer]

Google is starting to act like the collective...
I'll try this. Two browsers for the single task of avoiding work is unacceptable.

Agree on both.

Since I've changed this setting, no more timeouts but I still cannot upload an attachment from chrome or IE

How to:
Click the wrench
options
under the hood
uncheck the box next to "Predict network actions to improve page load performance"
close tab
you may still have to flush the cache afterwards