Oh yes, the good old volatility chapter: Logger determines single point of failure for a logger connection to a structure and attempts to allocate (if possible) so that the connection is non-volatile. Single point of failure in turn determines if a log stream is duplexed (using duplexmode(cond), which is the default).
Sam, 1. what duplexmode are you using? 2. when you specify non-volatility for the CF, will your log stream be in a single point of failure situation? (Remember that CF volatility is only one criteria) If the answers are 1 COND and 2 NO, then you may see less cpu consumption because duplexing is not done anymore. Otherwise, I don't see how it will help performance. I think. I have no clue if we have an internal battery :-) Best regards, Barbara -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
