On Thu, 30 May 2019 22:12:13 -0500 Michael Hochee <[email protected]> wrote:
:>I recently added the BNDRY=PAGE parameter to a set of STORAGE OBTAINS which acquire storage areas of various sizes from several low private subpools. My intent was a reduction of CPU used by subsequent MVCLE instructions, as ADM would more likely be employed for MVCLE executes, since the storage areas involved were page aligned (apparently an ADM pre-req.) Unfortunately my initial testing revealed a significant increase in CPU consumption, rather than a reduction. :>I did a few searches of the IBM-MAIN archive and found nothing involving increased CPU overhead resulting from BNDRY=PAGE usage. Any thoughts on what might be causing the elevated CPU? Again, the only change made was adding BNDRY=PAGE. (I have since backed the change off, tested, reapplied the change and tested with the same results) Might it be that the page aligned storage is less likely to be assigned at GETMAIN time, waiting for first reference, thus guaranteeing page-fault processing? Try fetching/altering one byte on the page before doing the timing. -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
