Server Issues
Over the last week we've been having a number of server issues. As far as we can tell this simply seems to be due to the steadily growing traffic, so it's not a terrible thing. Still we need to address it and we are going to right away. I've included our current thinking below, but it is a bit technical in nature. Still I want people to know that we are actively addressing these issues.
[Technical Answer]
Right now it appears that the biggest problem is that our Apache server is spawning too many threads to handle the many requests coming through. We are going to look into potentially moving all images to S3, to reduce the load on our Apache server or potentially purchasing another dedicated application server for CommunityWalk. Right now we are leaning towards the S3 solution, but we are still not 100% sure that it would solve our problems.
[Technical Answer]
Right now it appears that the biggest problem is that our Apache server is spawning too many threads to handle the many requests coming through. We are going to look into potentially moving all images to S3, to reduce the load on our Apache server or potentially purchasing another dedicated application server for CommunityWalk. Right now we are leaning towards the S3 solution, but we are still not 100% sure that it would solve our problems.
posted by The Entreprexplorer at
7:53 AM
1 Comments:
Some of the things that can help with your issue [in order of importance]...
1)Adding more RAM to the server
2)Setting the following httpd configuration directives to your needs...
KeepAlive, KeepAliveTimeout, MaxRequestsPerChild, ServerLimit, MaxClients, MinSpareServers, MaxSpareServers, StartServers
3)Using different servers for static and dynamic content, with the ProxyPass directive.
4)Using a lightweight server such as tux or thttpd as the front-end server.
DeveloperSide.NET
By
Anonymous, at 5:17 PM
Post a Comment
<< Home