dealing with CPU hogs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: <users@xxxxxxxxxxxxxxxx>
Subject: dealing with CPU hogs
From: "Tony Rice \(trice\)" <trice@xxxxxxxxx>
Date: Fri, 6 Jul 2007 16:30:32 -0400
Authentication-results: rtp-dkim-1; header.From=trice@xxxxxxxxx; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
Reply-to: users@xxxxxxxxxxxxxxxx
Thread-index: AcfADIA+LDIm7aOcTN+hAJNDDlRdzw==
Thread-topic: dealing with CPU hogs

Any suggestions on configuration changes I can make to lessen the impact of CGI scripts which become CPU hogs?

I'm running an apache server with about 150 virtual servers. Ocassionally an errant script will go nuts and consume 100% of the CPU. It's really bad when a spider finds one of these poorly written scripts and calls it a few thousand times.

I'm monitoring the server and killing off processes that run too long, that catches most issues before they impact performance too badly, but not when a spider is behind the requests.. Any other suggestions? Can consistent connections be throttled on a per client IP address basis? Can server processes be controlled on a per virtual server basis?

Follow-Ups:
- Re: dealing with CPU hogs
  - From: Nick Kew
- Re: dealing with CPU hogs
  - From: Hamilton Vera

Prev by Date: Apache 2.2.3: "You don't have permission to access the requested directory" for public_html directories w/o index.html
Next by Date: Re: Apache 2.2.3: "You don't have permission to access the requested directory" for public_html directories w/o index.html
Previous by thread: Apache 2.2.3: "You don't have permission to access the requested directory" for public_html directories w/o index.html
Next by thread: Re: dealing with CPU hogs
Index(es):
- Date
- Thread

[Index of Archives] [Open SSH Users] [Linux ACPI] [Linux Kernel] [Linux Laptop] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Squid] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper]