Date: Sat, 30 Jan 1999 20:09:08 -0500 (EST) From: "John S. Dyson" <dyson@iquest.net> To: tlambert@primenet.com (Terry Lambert) Cc: dyson@iquest.net, tlambert@primenet.com, dillon@apollo.backplane.com, wes@softweyr.com, toasty@home.dragondata.com, hackers@FreeBSD.ORG Subject: Re: High Load cron patches - comments? Message-ID: <199901310109.UAA60804@y.dyson.net> In-Reply-To: <199901310030.RAA26908@usr04.primenet.com> from Terry Lambert at "Jan 31, 99 00:30:47 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert said: > > > > Throttling fork rate is also a valuable tool, and maybe a hard limit > > > > is good also. It is all about how creative you are (or want to be) > > > > in your solution :-). > > > > > > I wonder about an explicit yield being a result of your standard > > > fork(2) call invocation... the more processes in read-to-run, the > > > longer you get to wait before your next fork... > > > > If one did that, it would be wise idea to only do the yield when > > it would be profitable. > > Do you mean "only when someone is actually waiting to run", or do > you mean "as defined by the results of some as yet undefined > profitability calculation"? > Maybe yes to both or either. I did experiment with that, with indeterminate results (except hurting low level latency experiments.) I didn't (about 2yrs ago) have enough info to move further, and was working on other things. It would be an interesting investigation. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. 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?199901310109.UAA60804>