Thanks for your ideas, Max. It went all day yesterday without
saturating, but when I got up this morning, there were dozens of
httpd processes, and lookupd was soaking up 85% of the CPU, load
average 12!
On 13 Jun 2005, at 15:38, Max Roeleveld - Qualion Internet Services
wrote:
Op 13-jun-05 om 22:17 heeft Jan Steinman het volgende geschreven:
what kind of sites are you hosting?
My sites are of three kinds: hand-coded static sites (very snappy), a
hand-coded PHP/MySQL artists' gallery package (still pretty
lightweight), and MediaWiki (slow as a slug :-).
When I have this problem, it isn't necessarily the slow MediaWiki
sites that are stuck. But it's always a spider at the end of the log.
(Of course, that may simply be statistical probability... :-)
Depending on how much memory the G4 has...
1.12GB. It's been plenty so far.
is Apache doing DNS lookups?
It's not supposed to. My logs all have IP addresses in them.
When top reaced 0% idle, was named anywhere near the busiest
processes (top -u)?
No. As noted, lookupd seems to be the major hog. Even after reading
the man page, I can't claim I understand why. It seems to be serving
as a cached for named, among other things?
Of course, blocking all search engine bots is not a long term
solution.
Exactly! (Although I don't feel too bad about blocking msn... :-)
How many child processes is Apache instructed to keep right now?
The default. I think it's 5.
What happens if you increase it...
I don't think that's the problem, because:
Does the slowness persist (if you do nothing), or does it fade away
after the bots did their thing?
It persists forever, or until I restart Apache, whichever comes
first! :-)
During the slowdown, what are the most CPU-hungry processes (top -u)?
I have not actually done top -u, but in terms of %CPU, it is always
lookupd.
Does Apache complain about anything (in the error log)?
It has a few things it doesn't like -- nothing that would seem to tie
up lookupd. Missing files, a few PHP errors that I should clean up,
but have been there forever (undefined index, undefined variable, etc.)
How about memory? How much of it is there? How much of it is free?
How about VM?
Unfortunately, it's purring along just fine at the moment. I keep top
running in an ssh terminal to keep track of it. I'll note these
things next time. But it doesn't seem to be thrashing when it slows
-- just idle time goes away and the CPU is saturated. If it were VM
related, I'd expect other symptoms.
(Yes, I know, it's bad manners to answer a question with more
questions =] )
No, thanks! I've been administering Unix systems for 20 years, but am
at a bit of a loss on this, so more questions are good!
Here's what top -u looks like at the moment, when it's working fine:
:::: The tragedy of modern war is not so much that young men die but
that they die fighting each other... instead of their real enemies
back home in the capitals. -- Edward Abbey
:::: Jan Steinman, http://www.Bytesmiths.com/Events
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Web-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/web-dev/email@hidden
