|
Rick, Not that I'm trying to defend the bloody governor, but there are also normal functions performed by the CFINT01 task that typically take 3% to 15% of the CPU. Whenever I caught the governor being triggered on the server boxes I used to work with, the share of CPU it was grabbing was usually 30% or more. Just now on the 620-2180 that we have here (which is not a server system and is supposed to have a completely unfettered Apache CPU running at full speed), CFINT01 took 3.2% over a 5 second timespan, and 4.4% over a 1 minute 41 second span. This is consistent with what I normally see on this box. It's interesting that IBM'ers are actually starting to use the term "governor" - when I used it 3 years ago they did everything they could to avoid it. ;) Dave Shaw -----Original Message----- From: Rick DuVall [mailto:R_C_DuVall@daaokc.com] Sent: Thursday, January 13, 2000 9:40 AM To: MIDRANGE-L@midrange.com Subject: Re: Have you read this? YEAH! I sometimes pull up wrksysact and watch my good friend CFINT01 sucking up 5 -15 % of my processor. I love it! I was really concerned about what I would do with all that excess processing power! I suppose I have no valid complaint in this matter but it sure does PI** me OFF! Regards Rick ----- Original Message ----- From: <Jdedwardsconsult@aol.com> To: <MIDRANGE-L@midrange.com> Sent: Thursday, January 13, 2000 1:32 AM Subject: Re: Have you read this? > Oh yeah... I've got a comment... we bought another company and acquired their > interactive users. When we exceeded the interactive "allowance" a wonderful > job/task/whatever called CFINT01 kicked in and basically took over the CPU. > I was told by IBM that it was like a "governor". Not only did it insure we > would not be able to use more interactive CPU than we paid for... it made > sure we couldn't get any work done at all. We have since upgraded from an > S30 to a 730... at the mercy of IBM who took us for a nice ride in the > process. > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.