For the older versions of RedBack that was a standing recommendation: Set the GC purging criteria to something reasonable, but the interval sky high to "run never". Then run REDBACK.GC from a PHANTOM, crontab or Windows scheduler (whichever suits).
Other standing advice: 1. Set WWSTATE to large (10's of K), static hashed, and a large block size 2. If upgrading to a version of RedBack that used WWSESSION to record and purge WWSTATE then manually purge WWSTATE on your upgrade (WWSESSION is an invert file "index" - and has no entries, so nothing left in there historically will be purged). 3. Positively set the Garbage Collection parameters - even if you don't need to change them. One of the RedBack versions had invalid parameters on installation and a positive change was needed to fix it. Notes on stuff that people tend to forget: * STARTBACKEND=1 for production use, 2 for developers * Turn of the stats for marginally better performance in you don't need stats. * Don't use session variables in IIS Regards JayJay -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Pflueger Sent: 30 May 2007 17:34 To: u2-users@listserver.u2ug.org Subject: Re: [U2] RedBack Garbage Collection On 5/30/07, daverch <[EMAIL PROTECTED]> wrote: > Just run REDBACK.GC from your account with RedBack installed on it or from > RBDEFN account. > We run REDBACK.GC at the end of a nightly process we run as a phantom and works very well. Just thought that little 2 cents worth of info. ;) Andy ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
