Knowledgebase

I am getting connection timed out problems when server load is at 10 or more

Posted by chasebug, 09-09-2010, 10:34 AM
When going to my site, it just stays at "Connecting to....." and then comes a timed out error. Is there any way to tweak the server so that it will won't get the timed out error? I don't care if the site loads slow, just as long as it can load.

Posted by Fizzadar, 09-09-2010, 10:38 AM
You should really check out what's causing such a high load to fix that. Allowing longer timeouts will only add to the load.

Posted by net, 09-09-2010, 10:42 AM
Moved > Hosting Security and Technology.

Posted by GOT, 09-09-2010, 10:45 AM
Having timeouts with a load of ten is not surprising. You should take a look at top while the load is high to determine where the problem is.

Posted by eSupun, 09-09-2010, 12:03 PM
Try, to see which is using much CPU.

Posted by matt2kjones, 09-09-2010, 12:54 PM
Has this server been managed for you, or has it been optimised at all? It may just be a case that your website has outgrown the default configuration for mysql and other server processes. Tuning some configuration files should lower your loads, but it really depends on the specs of your server. Maybe post results from the command "free" and "cat /proc/cpuinfo" and also paste your mysql config and the resources section of your httpd.conf. It may also be a poorly coded script causing the high loads. Do you have daily visitor counts for your website, and what software does the site run... eg cms software, forum software, any plugin's or addons.

Posted by Syslint, 09-09-2010, 01:12 PM
What is your hardware configuration ? is it shared , dedicated or vps ?

Posted by Cyrus255, 09-09-2010, 01:14 PM
Dear gosh, at a server load of 10?! How many processors you got on your server? Is this really a surprise... I remember getting some when I'd peak up to 3 or 4.... The way I solved that issue was with caching... a server-wide cache that I paid for the company to install. (x-cache is my personal fave for that). Never had a overload since, even with massive traffic spikes. Definite improvement (also cut down bandwidth usage significantly).

Posted by netmar, 09-09-2010, 11:39 PM
A load of 10 means that you have 10 processes waiting their turn to use the CPU (or if you're using Linux for CPU or disk I/O). Either way, if that load stays around 10, then given that most processes execute in milliseconds, you are having serious problems with either memory (swapping memory to disk drastically slows execution as well as blocking other I/O) or with a flood of new processes. As someone suggested above, top should give you an idea of what those processes are, as would ps. You may also want to check memory usage with the free command -- if you are using any significant fraction of your swap space, then you have problems.

Posted by chasebug, 09-10-2010, 02:55 AM
I've been trying to optimize this server all day. The problem is disk i/o, top shows wa% at 50-70% I've run out of ideas on how to improve performance.

Posted by netmar, 09-10-2010, 07:21 PM
Try checking dmesg to see if you're having any hardware issues with the drive. The only legitimate reason that I can think of for that much hard drive usage is memory swapping, and/or constantly copying large files. If you're not doing either of the above, then you may have an issue with either the controller or drive hardware.

Posted by Hillockhosting, 09-11-2010, 02:15 AM
check the sar results.. The time out could well be due to high IO

Posted by chasebug, 09-11-2010, 06:57 AM
I've gotten loads down to about 5 via some tweaking, the connection don't time out anymore BUT I can't download faster than 100K/s from the server. The wa% is at 60-70% constant on this server. Nothing in swap.

Posted by matt2kjones, 09-11-2010, 07:03 AM
where is your website served from.... Find out the folder then type lsof /path/to/website to see how many open files there are..... With that high I/O wait that is obviously what is causing your high load averages. Again, look at MySQL as well, as you may be wasting disk I/O on your database server which could be lowered down by caching more agressive. Failing that.... Faster disks, or move to a high performance raid such as raid 10



Was this answer helpful?

Add to Favourites Add to Favourites

Print this Article Print this Article

Also Read


Language:

Client Login

Email

Password

Remember Me

Search