| 1 |
I would suggest mod_throttle might be helpful, but it's still only for |
| 2 |
Apache 1.3 AFAIK. If there's an Apache 2.0 equivalent, perhaps someone |
| 3 |
on the list will know. |
| 4 |
|
| 5 |
Bart Braem wrote: |
| 6 |
|
| 7 |
> On Mon, 21 Jun 2004 10:28:55 -0700 (PDT), Kashani |
| 8 |
> <kashani-list@××××××××.net> wrote: |
| 9 |
> |
| 10 |
>>On Sat, 19 Jun 2004, Bart Braem wrote: |
| 11 |
>> |
| 12 |
>> |
| 13 |
>>>I am running a server that sometimes get's a lot of traffic and we |
| 14 |
>>>experienced some problems due to the amount of processes. We are |
| 15 |
>>>considering using nptl for our apache2 server, does that work? Is it |
| 16 |
>>>considered stable enough? |
| 17 |
>>> |
| 18 |
>>>Thanks for any advice! |
| 19 |
>> |
| 20 |
>> Generally your module and libs support goes to hell when you turn |
| 21 |
>>on threading in Apache2. mod_php itself is considered to be thread safe, |
| 22 |
>>but adding in various things like imap support will break it because the |
| 23 |
>>imap libs aren't thread safe. Most of the people who are using threaded |
| 24 |
>>Apache2 are using it for very specific applications where they can avoid |
| 25 |
>>supporting the usual module madness that general hosting requires. |
| 26 |
>> |
| 27 |
> |
| 28 |
> Okay that sounds reasonably good... |
| 29 |
> |
| 30 |
> |
| 31 |
>> There are a number of performance hacks you can do such as running |
| 32 |
>>multiple webservers, one for dynamic content and one for static content. |
| 33 |
>>If you want to talk more about what you're doing and need to support I can |
| 34 |
>>try to make some suggestions. |
| 35 |
>> |
| 36 |
> |
| 37 |
> Okay the situation is as follows: we have a server running that uses |
| 38 |
> PHP to dynamically generate images with GD. That goes pretty fast, but |
| 39 |
> when someone uses spiders to download our entire site it just crashes |
| 40 |
> away because of hundreds of processes. |
| 41 |
> We did manage to stop the spidering by blocking their user-agents but |
| 42 |
> if some spider identifies itself as Mozilla we're out of bussiness... |
| 43 |
> Another thing we did was installing MMCache and that solves some |
| 44 |
> problems but it's just a patch not a real soltuion... |
| 45 |
> So we consider using nptl to have less processes (the php processes |
| 46 |
> themselves are very small) and more threading. |
| 47 |
> Would that be a good idea? Do you have any other suggestions? |
Archives