1 |
On 03/07/2013 03:45 PM, Grant wrote: |
2 |
>>> I lowered my MaxClients setting in apache a long time ago after |
3 |
>>> running out of memory a couple times. I recently optimized my |
4 |
>>> website's code and sped the site way up, and now I find myself |
5 |
>>> periodically up against MaxClients. Is a RAM upgrade the only |
6 |
>>> practical way to solve this sort of problem? |
7 |
>> |
8 |
>> Use a reverse proxy in caching mode. |
9 |
>> |
10 |
>> A request served up by the proxy server is a request not served up by |
11 |
>> Apache. |
12 |
>> |
13 |
>> Squid, nginx and varnish are all decent for the purpose, though squid |
14 |
>> and nginx are probably the more polished than varnish. |
15 |
> |
16 |
> Thanks Michael, I think I will set up nginx to serve my images. That |
17 |
> should take a big load off apache. Is nginx still beneficial when |
18 |
> using the Worker MPM? |
19 |
|
20 |
It...depends? |
21 |
|
22 |
nginx in reverse caching proxy mode will simply serve up objects before |
23 |
the httpd it's protecting has to deal with them. Whether the type of an |
24 |
MPM makes a significant difference on nginx's value depends more on what |
25 |
kind of work you are (or aren't) asking Apache to do. I really couldn't |
26 |
answer that for you without knowing the details behind what you're |
27 |
running on top of Apache. |
28 |
|
29 |
> |
30 |
> Should I be OK with NGINX_MODULES_HTTP="" in /etc/make.conf if I'm |
31 |
> only serving images? |
32 |
|
33 |
No idea. I've not used nginx, but it's highly recommended and widely |
34 |
used for the purpose. You'll have to dig into the docs yourself. :-| |