D
dbeavon
Guest
>You can start the database with low value of the -B/-B2. It will imitate the unused buffer pool. But it's still not enough for the fair tests. Yes, using a very small -B/B2 is the obvious test that bypasses OE buffering. But to make things fair, even the *first* execution of some custom ABL code should be allowed to use a little bit of database buffering. I understand about file system caching. That is between me and my operating system. Obviously the thing I'm looking for OE to do is help me troubleshoot its own RDBMS buffers in a more flexible way. I'm waiting for someone to tell me to submit a feature request ... but the fact of the matter is that there is probably already a feature in there that is internal or is being hidden from us. I was hopeful that -Bp was finally the answer that I was looking for, but then someone says that the clients private buffers are added to the public buffer pool when the client with the -Bp option disconnects. What use is that anyway? The only reason that -Bp was specified in the first place was because the client was going to use data that wouldn't be of interest to other database clients. (Or else there should be a -Bpx that tells Progress not to put the clients private buffers back in the public buffer pool when the client disconnects.)
Continue reading...
Continue reading...