G
George Potemkin
Guest
I was mainly wondering why there is a difference between the self-service and remote clients. The similar situation exists with promon and ACO (Area Control Object) blocks. Updating the activity counters in promon will read ACO blocks from all data areas. The _AreaStatus VST and prostrct statistics read them too. But the information stored in these blocks seems to be already stored in some structure in shared memory. At least "find by recid" where recid is higher than area's HWM will not create db request. And it will not read ACO block either. promon/R&D/5. Adjust Monitor Options/7. Change working area I can choose 3. Primary Recovery Area In this case promon will NOT read ACO blocks. Can I still rely on data reported by the activity screens? I don't see any problems with that data. Then why promon is reading ACO blocks by default? They are on LRU chain. Promon does have the problems when there is the contention on LRU latch. What is the best solution to avoid these problems? To set Primary Recovery Area as a working area? Or to put ACO blocks into the dynamically allocated "alternate buffer pool"? Both solutions seem to work. A solution with working area is simplier but I feel less comfortable with it because I don't know why promon reads ACO blocks.
Continue reading...
Continue reading...