HELP, my servers can't handle the loads!
 

I just purchased my fifth server from EV1.net and it is slower than ever.

I have 300 clients downloading from one of my main site through this server (only one site on this server) Intel Dual Xeon 2.4 Server with 2000gb transfer.

How can I optimize this to handle 600 or more at one time?

Is there a managment company that can do this for me?

help, I'm losing sales. :helpme

redirect all your traffic to my sites
it will solve the problem ;)

Might try getting a MANAGED host instead of ev1

There are a few management companies that could help you, or you could hire a tech to fix your problem. Talk to JFPDude, he may be able to help you out.

What OS do you run?

I could help ya for a price

I would suggest JFPDude too. Might want to switch hosts too but that is your choice.

OS - Linux Ensim Pro for Red Hat Enterprise

I only upload twice per day to my three servers that handle my TGP gallery posts. This is the only thing these servers do, gallery submissions.

300 users on one server seem small, but I don't know much about this subject.

all I know is how to get traffic.

What type of connection are your servers on? The problem would not be the server load but connection load if they are just gallery pages..

Could you define users. Are they clients that use some sort of submit script through your site/server?

Here's a bump.


:)

Kill your KeepAlives maybe? I know those slowed my server down a lot.

gallery submissions are causing this load average?

hah.

you need to learn how to tweak apache.

what company can twik my apche?

You have to change your Apache HARD_SERVER_LIMIT and update httpd.conf to handle more requests.... hire a Linux System Admin

Fris - I get a lot of hits. 205,720,166 today so far. Sessions is what I have to deal with 18,057 today so far.

what he said.

or maybe you should hire someone to do it for you .

18k sessions isnt suppose to cause load on 1 servers if you tweak it correctly...

i had similar issues and juicy links referred me to JFPdude and he fixed.

note: these were servers setup by webair, and as others have stated you need your apache custom tuned for load.

:banana Thanks for the props guys ...

If this is still an issue hit me up on ICQ 4433144

debbieN - send me your apache config file and I'll add some the tweaks that should help. No cost - they're basic, and will see if it is the problem or at least pinpoint where the problem is.

icq me 283914791

thanks borked but I just spoke with the master - JFPdude

again thanks GFY for the correct information.

your gonna blow your load

"my servers can't handle the loads!"

Then help the servers, just swallow! :)

I would turn off keepalive or at least turn the timeout down to 1
strip out all modules you don't need to get the httpd process size down then
rebuild with hard_server_limit 1024 and up maxclients to fit the RAM so it doesn't swap

You reallly should consider fully managed hosting ...

hire a sys admin to look after your server(s)

whats th eURL to one of your galleries, your problem may be something else

You shouldn't have problems with just 300 clients. Call Webair mike. See sig.

For apaches... pre 2.0...

Apache Performance Boost
By: Chris Jester ( [email protected] )

If you are experincing long delays while "Waiting for reply...." with Apache servers you may try the following hack I use frequently to speed up your systems performance. Apache comes with a limit of 256 Child Processes defined in its hard server limit (in the source code). This can kill apache when it is used for a very very busy site.

Normally in the httpd.conf file you can only set a maximum of 256 MaxClients. This is not enough for a busy site. To change this limit (which the makers of apache suggest as well), edit src/includes/httpd.h and change the value of HARD_SERVER_LIMIT. Bump it up to 1024, then set your httpd.conf files MaxClients to like 512. That should be ample. Re-compile apache and you are done.

Note: Linux itself has a "Max Processes" per user limit. Add this to your root .bashrc file:

ulimit -u unlimited

You must exit and re-login before starting your new apache! Otherwise you will run into problems. To verify that you are ready to go, make sure that when you type ulimit -a as root, it shows "unlimited" next to max user processes.

(note: you may also do ulimit -u unlimited at the command prompt before starting httpd instead of adding it to the .bashrc file, but I always forgot, so I just added it in the .bashrc file as a safety net.. Another good place to put ulimit -u unlimited is in the httpd startup file in /etc/rc.d/init.d)

Here is how you can find out if this might be the problem:

On the command line, type: ps -aux|grep httpd|wc -l

It will return a number. If this number is about 300ish or close, but not above,
then its most likely the problem I solve above.

For Apache 2.0, its EASY as pie to fix:

Set these like this:

Timeout 60
KeepAlive On (Set this to off if your site is only doing CGI redirection, but on in most all other cases)
MaxKeepAliveRequests 0
KeepAliveTimeout 20
ServerLimit 1000

<IfModule prefork.c>
StartServers 100
MinSpareServers 5
MaxSpareServers 30
MaxClients 1000
MaxRequestsPerChild 0
</IfModule>

Note, this is all dependant on RAM and PROCESSOR
so if your notice your ram is all eaten up, reduce MaxClients to like 700

(if you didnt know, this is in the file /etc/httpd/conf/httpd.conf)

Edit that file, then do this:
service httpd restart

some good free advice from splitinfinity ;)

Suggestion to all: Dont use .htaccess files.
Instead, use the httpd.conf file.
Reason? Performance impact.
Every file that is served by apache is in a directory tree....
And the server needs to check EVERY DIRECTORY along the file
path for an .htaccess file, just to make sure theres none there
and/or of there IS one there...

So think of it like this....
You have something.gif and someone is loading it right now...
Apache says, oh ok....
Lets see... the file is in /home/one/two/three/four/five
Then it says...
is there and .htaccess file in /home?
is there and .htaccess file in /one?
is there and .htaccess file in /two?
is there and .htaccess file in /three?
is there and .htaccess file in /four?
is there and .htaccess file in /five?

Imagine the disk load and etc if you have like 50 thumbnails on your page?

Food for thought GFY'ers
:-)

How would you for example prevent hotlinking in the httpd.conf file?

The same way you do it in an .htaccess file, but you put it in the Virtualhost directives in your httpd.conf instead and delete your .htaccess file.
:-)

By doing it that way, apache only has to load them once.... not per hit