--------------------------------------------------
From: "Nicholas Sherlock" <[email protected]>
Sent: 28 January, 2010 9:51
To: <[email protected]>
Subject: [us...@httpd] Re: Runaway Apache Process
On 28/01/2010 8:30 p.m., Daniel Reinhardt wrote:
From: "Dan Bunyard" <[email protected]>
@Daniel Reinhardt
Here are the full specs:
CPU: Pentium Dual Core E2220 @ 2.40GHz
RAM: 5GB DDR2 PC2-6400 @ 800MHz
Hard Drive: Western Digital SATA II 500GB
I'm running Fedora 12 (Constantine) on it currently and Apache version
2.2.14 with PHP version 5.3.1 and MySQL version 5.1.42.
Dan,
For one thing I would get a beefier CPU. Your CPU isn't fit to be a
serving machine it is rather slow. You need to be running a workstation
grade CPU Like a Intel Q6600 or a E6400.
For 11K hits a month? That's one hit every four minutes. From the log snippet
posted, it seems to be a simple mixture of blogs and forums. Hardly
supercomputer stuff. A slow single-core would serve it just fine.
Cheers,
Nicholas Sherlock
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
" from the digest: [email protected]
For additional commands, e-mail: [email protected]
Nich,
Obviously not in this case as this person wouldn't ne here complaining about
apache and its processes. The issue here is the CPU is too weak even if it is a
2.4Ghz processor. The E2220 isn't suitable for a server processor. Its
strictly for home computing. I help remote administrate a server that supports
10 Domains and 5 E-Mail Servers that receive a whole lot more traffic on a P3
933Mhz and these issues are not occurring there, and the settings for Apache are
default.
Thanks,
Dan
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [email protected]
" from the digest: [email protected]
For additional commands, e-mail: [email protected]
