D
dbeavon
Guest
Reading about "-Bp", it seems to say that the buffers are stolen from the public (-B) buffers anyway, so either way the public buffers are being consumed by the backup. Hopefully a backup isn't so greedy as to "wipe out" all available buffers. It would seem foolish considering most of the data is used on a one-time basis and won't be accessed again. Since we are talking about this "BP" client parameter that is new to me, I have a related question. In the past I had wondered if there was a way to flush clean buffers in order to test the performance of reads from the I/O disk system. (see community.progress.com/.../86187 Would the Bp option serve the purpose of effectively flushing my buffers? In other words, whenever I restart an ABL client with private buffers, will all the initial reads to to the disk before it starts using the data cached in buffers? Nobody had suggested this as an option when we were talking about flushing buffers, and the best ideas were either to restart the entire database or perform a long-running dbanlysis to flush out the shared buffers (maybe in a similar way as what you say happens during a backup).
Continue reading...
Continue reading...