| 1 |
On Fri, 2004-05-14 at 07:01, Raymond den Ouden wrote: |
| 2 |
> Oh sorry... |
| 3 |
> |
| 4 |
> I forgot to mention the server details |
| 5 |
> Apache: 2.0.49-r1 |
| 6 |
> Mod_PHP: 4.3.6-r1 |
| 7 |
> OpenSSL: 0.9.7c |
| 8 |
> Kernel: 2.4.26 |
| 9 |
<...> |
| 10 |
> When looking around I ran into was DO NOT USE Apache 2 and PHP in a |
| 11 |
> production environment :( |
| 12 |
|
| 13 |
Many people are using apache 2 in production with PHP, and most of them |
| 14 |
(including me) find that it performs far better than the rapidly aging |
| 15 |
(and increasingly irrelevant) apache 1.x versions. |
| 16 |
|
| 17 |
> Also I already tried to look at ulimit before you mentioned, but it did |
| 18 |
> not give really satisfying answers :( |
| 19 |
> |
| 20 |
> What could be a memory consuming item in the site might be: |
| 21 |
> - a dynamically generated image (1x1) pixel, so that should not be too |
| 22 |
> expensive for 800 pageviews a day, the script cleans up the mess itself. |
| 23 |
> - A download of 50 Meg, which was streamed by PHP for leechprotection at |
| 24 |
> the same time gzip was on, this could be a really memory consuming option. |
| 25 |
> - The CMS (Mambo Open Source 4.5 1.0.7) |
| 26 |
|
| 27 |
When PHP processes files, it often uses two to four times the file size |
| 28 |
in memory to handle it. I'm on the Squirrelmail (PHP webmail) core |
| 29 |
team, and one of the most common problems people have is with large |
| 30 |
attachment (file) handling causing PHP to use too much memory, crash, or |
| 31 |
hang. If the PHP script times out while handling this file, all that |
| 32 |
memory may not be released cleanly. |
| 33 |
|
| 34 |
Mambo, and other CMS and portal applications, contain many plugins with |
| 35 |
widely varying programming quality. Try turning off all the Mambo |
| 36 |
plugins to see if this helps things at all. |
| 37 |
|
| 38 |
Regards, |
| 39 |
|
| 40 |
- Brian |
| 41 |
|
| 42 |
|
| 43 |
-- |
| 44 |
gentoo-security@g.o mailing list |
Archives