Are you trying to migrate from CentOs & Apache to Fedora & Nginx? - Feed Post from spanz to beeant
Are you trying to migrate from CentOs & Apache to Fedora & Nginx?
You're tireless!
Just curiosity, why? Is the Fedora machine another server?
You're tireless!
Just curiosity, why? Is the Fedora machine another server?
posted by spanz
Comments 12
Im trying to use nginx with FastCGI and php-fpm. But I didnt succeed...
Sometimes there are above 40 ++ users online in JCJP at the same time and the page could not be loaded... so frustrating.
I want the site to grow but when there are 40 above users online, the page cant be loaded ??? ahhh
I think I'll just leave it as it is now, with Apache and prefork MPM...
Do you know anything about these things? like switching Apache from prefork to worker mpm?
Sadly, no. I have no idea about those things, but making a bulletin thread about it won't hurt. There are experts everywhere.
Well, I know one thing: 40 users should be a piece of cake for every http server out there, so something's definitely wrong.
I'm sure there's a lot of documentation, so take your time and fix it.
It's an important issue, so if you must shutdown the site for a while, please do it (make an announce, though).
Aren't there distros with Apache worker mpm preconfigured?- i dont know, but this server is preconfigured with CentOS.
ya 40 users should be a piece of cake, I dont know why this happens.
I will just leave the server as it is now.
I tried in the old server with fake traffic. it was ok.... even it only has 256MB of RAM. Something is wrong... - Anoo... I don't really know what I'm talking about but I see a difference between JCJP and all other sites I've tried today.
Looking at HTTP header requests & responses in FireBug, all the requests include:
Keep-Alive 115
Connection keep-alive
But all JCJP responses include:
Connection close
(That's even for static content)
In all the other sites I've tried, the HTTP response header includes:
Connection keep-alive
Or in other cases, there's not a Connection field.
It seems your server doesn't permit HTTP persistent connections at all.
Are you blocking keepalive connections? That will produce a lot of unnecesary traffic, ne?
As I don't really know this things, this is probably a stupidity, so you are free to kick my ass and shut my mouth.
- thats bcos I disabled keepalive connection. I've been told that keepalive connection will take some resources of the server. so I turn it off.
If you take a look at high traffic sites HTTP header requests, it seems like most of them closed the connection. try facebook - Please, don't pay atention to me.
I don't want to waste your time, but your example is not valid.
Facebook uses keep-alive for its static contents.
Same for Yahoo.
Same for Microsot.
Youtube and Google don't say anything, so I don't know.
I can't find a site like JCJP.
By the way, Youtube is using Apache with lighttpd as a proxy for static content.
Other sites use Apache & nginx for static content.
Sorry again. My ass is ready for your kick (with k!). :p
- I just checked in http://web-sniffer.net/, it says, connection close. maybe if its not logged in?
I will research some more about KeepAlive connection - How strange!
Under FireBug, the Facebook.com main page response is closed, but all the rest are keep-alive.
For example, this is a .png url from the main page:
http://static.ak.fbcdn.net/rsrc.php/zEX21/hash/75j4m1ms.png
Response header under FireBug:
Server: Apache/1.3.41.fb2
Last-Modified: Sat, 01 Jan 2000 00:00:00 GMT
Content-Length: 2209
X-Cnection: close
Content-Type: image/png
Cache-Control: public, max-age=25573840
Expires: Wed, 09 Mar 2011 19:16:37 GMT
Date: Mon, 17 May 2010 19:25:57 GMT
Connection: keep-alive
But if you test that url in web-sniffer.net you get:
Server: Apache/1.3.41.fb2
Pragma:
Last-Modified: Sat, 01 Jan 2000 00:00:00 GMT
Content-Length: 2209
X-Cnection: close
Content-Type: image/png
Cache-Control: public, max-age=25573655
Expires: Wed, 09 Mar 2011 19:17:44 GMT
Date: Mon, 17 May 2010 19:30:09 GMT
Connection: close
How's that possible?
Anyway, the persistent connection is supposed to reduce the traffic reusing the connections, so it should reduce also the resources used in the server.
- web-sniffer.net sends its requests with Connection = close, so the response is going to be also close.
FireFox sends its requests with Connection = keep-alive
This probably explain the difference. - ok i will try to turn it on. and see what will happen.
I just turn it on now.
Thanks! - I tried to turn it on, and tried http://loadimpact.com/ and its dead at 10 clients.
I tried to turn it off, its still works at 10 clients but slow - Sorry to hear that. It was only an idea. :(