Date: Wed, 27 Jan 1999 08:56:35 -0700 From: Wes Peters <wes@softweyr.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Kevin Day <toasty@home.dragondata.com>, hackers@FreeBSD.ORG Subject: Re: High Load cron patches - comments? Message-ID: <36AF3733.E6DFEB9F@softweyr.com> References: <199901261853.MAA15095@home.dragondata.com> <36AE3981.C3F59FF1@softweyr.com> <199901262256.OAA22114@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon wrote:
>
> :Wouldn't it be cleaner to limit it by load average rather than number of
> :jobs? This would tend to allow small, one-shot cron entries that really
> :don't eat a lot of resources to continue running on time, while saving
> :the machine from the monster processes.
>
> No, this won't work at all. I have direct experience trying to
> regulate things by load average.
>
> The problem is that the load average takes too long to ramp up and
> ramp down. By the time it's ramped up, cron may have already forked
> a thousand jobs. Plus if the system gets loaded on its own, you risk
> an effective disablement of cron alltogether.
So this is why pmake drives our system load average up to 8-10 before
dropping back down to the assigned limit of 5, huh? Maybe we should
fix the load average computations as John suggested.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
http://www.softweyr.com/~softweyr wes@softweyr.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36AF3733.E6DFEB9F>