To: (The User)
cc: petar@fnal.gov,cdfdb-support@fnal.gov,cdfdb-cpu@fnal.gov
Subject: Database cpu usage

*************************************************************************
**      OFFLINE SHIFTER                                                **   
**      - Attatch the All_CpuHistory.png plot to the email, you can    **  
**        do this by saving the .png image from the cpu history        **
**      - Don't forget to put your name at the end of the mail         ** 
*************************************************************************


Hello,

The offline database monitoring has noticed a significant amount of CPU usage 
from your username.  Is there a chance that your job is behaving abnormally ?

The attached plot shows cpu usage as a function of time and user.

We are not trying to interrupt your work, you do not need to kill any jobs at 
this time.  We are trying to ensure that communal resources are not wasted, or 
put in danger of failing.  We have often found that simple changes can be made 
to code that can greatly increase their database efficiency, making them faster
 for users to run and reducing their overall load on the database.  

Please follow the instructions below.  Also free to contact the database 
support people at cdfdb-support@fnal.gov for help, and/or to pester the 
librarian for your software package for help in making these changes so your 
jobs will run faster.

You should definitely investigate the source of this problem with the 
above offered help, and follow the procedures listed below, as this 
is not a routine message.

One can investigate the database accesses more
closely by adding the following to your tcl file:

   action on "Name Action"
   talk ErrorLoggerManager      
      remoteDest         
         debug set true
         localFile set /yourpath/yourfile.db.log
         threshold set INCIDENTAL
         exit
      exit

The results will be captured to your indicated local file.

Note this is for debug purposes only; you can get rid of
these lines after capturing some examples and don't need to
use this for routine running.

After collecting this database log file, please run the following script on the
database log file:

   > setup cdfsoft2 5.3.3
   > $CDFSOFT2_DIR/DBUtils/scripts/DBLogParse.py /yourpath/yourfile.db.log

please take a look at the output, you might see a 
solution immediately.  If the solution does not jump out at you, then
please send a link to the database log file to 
petar@imapserver2.fnal.gov for detailed analysis.

Please note: The choice of version depends on the physics you are doing;
in general we suggest using version

   cdfsoft2 5.3.3

or higher of the CDF software.


Thanks,  

(YOUR NAME)
Offline Shift Person