Poor performance during log switches
From: Dana Smith <dsmith_at_velcro.com>
Date: Wed, 6 Jan 1999 14:31:45 -0500
Message-ID: <wUOk2.74$9u6.921_at_news15.ispnews.com>
We periodically experience poor performance (read this as everything stops) during log switches. During this period of time (4-5 minutes,) we will notice several new log files being created which implies a high volume of data changes within the database although we have not identified a consistent concurrent job or transaction executing. Eventually, after 4-5 minutes, everything frees up and functions execute normally. Afterward, we will notice the date of creation of the new log files as being separated by 1 minute and sometimes even zero minutes!
Date: Wed, 6 Jan 1999 14:31:45 -0500
Message-ID: <wUOk2.74$9u6.921_at_news15.ispnews.com>
We periodically experience poor performance (read this as everything stops) during log switches. During this period of time (4-5 minutes,) we will notice several new log files being created which implies a high volume of data changes within the database although we have not identified a consistent concurrent job or transaction executing. Eventually, after 4-5 minutes, everything frees up and functions execute normally. Afterward, we will notice the date of creation of the new log files as being separated by 1 minute and sometimes even zero minutes!
We have our archive log file set at 20M and we see typically 2-3 log switches per hour, which seems to be an optimal number.
Does this 20M size seem reasonable and is there some other configuration setting we should be looking at to to correct this behavior?
Thanks for any help in this area.
Mr. Dana Smith
Received on Wed Jan 06 1999 - 20:31:45 CET