• Subject: Re: Backup performance (CFINT)
  • From: John Earl <johnearl@xxxxxxxxxxxxxxx>
  • Date: Tue, 07 Nov 2000 04:15:33 -0800
  • Organization: The PowerTech Group


Larry Bolhuis wrote:

> During troubleshooting of some communications problems (specifically
> token-ring errors) we discovered that CFINT01 had taken over the entire
> system on a NON-Server box, 95% of CPU and over 95% of system memory.
> Discussing this with support they indicated there there are other tasks
> assigned to CFINTnn jobs besides 'CPU Burn' and some parts of
> communications recovery is one of these tasks.
> Therefore I wouldn't dismiss CFINTnn on non-server systems, it just
> isn't 'playing govorner' on those systems.

You're right that CFINTnn is more than just the 'CPU Burn' job.  If I 
understand it
correctly, CFINT stands for something like "Command Function INTernal" and is
essentially just an accounting entry that causes the performance tools to charge
System Internal CPU cycles to a big bucket called "CFINTnn" (where the nn equals
processor number).  This would explain why people report large amount of CPU 
usage on
non-server systems, and may also explain why some really bright people have not 
able to locate and change the legendary CFINTnn job.  :)


John Earl                    johnearl@400security.com
The PowerTech Group      --> new number --> 253-872-7788
PowerLock Network Security   www.400security.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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].