G
gus
Guest
a checkpoint can begin only immediately after a bi cluster has become full and the previous checkpoint ended. the backup program /does/ flush all modified buffer when it starts. thos get counted as buffers flushed because . . . flushes are flushes, regardless of the cause. a quiet point can also cause flushes. so does a database shutdown, but almost no one ever notices. regards, gus (gus@progress.com) "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian Kernighan > On Nov 26, 2015, at 5:54 PM, James Palmer wrote: > > Update from Progress Community [https://community.progress.com/] > > James Palmer [https://community.progress.com/members/jdpjamesp] > > I've started monitoring certain things on our main database more proactively, and one thing I'm doing is tracking the _ActSummary table every 15 minutes or so. I noticed in promon that our buffers flushed stat was higher than I'd expected so wanted to track down when this is happening. > > I've just looked at the report and at 19:00 2667 buffers are flushed. 19:00 also happens to be when the online backup started. Am I right in assuming that the backup is causing this, or do I need to look further? Is it a concern? > > Progress 11.5.1 on Win 2012 R2. > > We have 4 APWs. Yes 4. And at the moment we have 0 buffers flushed at any other time. I am trying to build a case for turning off a couple of these APWs and using their resources elsewhere! > > View online [https://community.progress.com/community_groups/openedge_rdbms/f/18/t/21635] > > You received this notification because you subscribed to the forum. To stop receiving updates from only this thread, go here [https://community.progress.com/community_groups/openedge_rdbms/f/18/t/21635/mute]. > > Flag [https://community.progress.com/community_groups/openedge_rdbms/f/18/t/21635?AbuseContentId=b37abab5-2e8e-4657-ba9c-c6a42c29783b&AbuseContentTypeId=46448885-d0e6-4133-bbfb-f0cd7b0fd6f7&AbuseFlag=true] this post as spam/abuse.
Continue reading...
Continue reading...