full, backed-up logs causing slowdown?

Hello. Sun Solaris Workstations running Informix 7.x. The logs (15 of them) are being automatically being backed up using "ontape -c" to /dev/null. We have a user reporting that when less than 1/2 the logs are 100% full (and backed up), the system runs very, very well. When more than 1/2 the logs are 100% full (and backed up), the system slows down. We can't figure out why this is happening. Any suggestions? Thank you. -- Joseph Kormann Joseph.Kormann@lmco.com Ph:732/450-7126 Fx:732/450-7153 "Heaven is a half-pipe!" - OPM

First know that if LTAPEDEV is set to /dev/null then you do not have to run ontape -c, each log is automatically trashed and marked 'B' backed up as soon as it is completed (or manually switched away from). Next, the assertion makes little sense, look for another cause. Art S. Kagel Joseph Kormann wrote: > > Hello. Sun Solaris Workstations running Informix 7.x. The logs (15 of > them) are being automatically being backed up using "ontape -c" to > /dev/null. > > We have a user reporting that when less than 1/2 the logs are 100% full > (and backed up), the system runs very, very well. When more than 1/2 the > logs are 100% full (and backed up), the system slows down. We can't > figure out why this is happening. Any suggestions? > > Thank you. > -- > Joseph Kormann > Joseph.Kormann@lmco.com > Ph:732/450-7126 Fx:732/450-7153 > "Heaven is a half-pipe!" - OPM

Am I missing something? If your LTAPEDEV=/dev/null, why are you doing an ontape -c ?