C
ChUIMonster
Guest
If your first session accesses more data than fits into whatever you defined for -Bp then the excess will result in buffers being evicted from -Bp. If nobody else referenced then then they are no longer in memory. If later on a 2nd session wants to reference some data that your first session referenced and that data is no longer in memory then it will need to be re-read from disk. It doesn't "go back to disk" -- it is simply removed from the list of blocks that are available in memory. (Unless you modified some data -- but this discussion is all about reads....) Offhand I'm not entirely sure what happens if -B is very large and underutilized compared to -Bp. I suppose that Progress *might* decide that if a block is being "evicted" from -Bp *and* there are unused -B blocks then it could kept around in memory just in case. It does not seem to me like there would be any harm to that -- except that it would have to be coded and every bit of coding means potential for bugs and unanticipated overhead. If it were me I probably wouldn't do it. It is far too speculative and the whole point of -Bp is that you are saying "I don't think anyone else will care about this data".
Continue reading...
Continue reading...