The usual C malloc() keeps track of allocated memory with data just before each allocated block.
As well as I understand it, GETMAIN works similarly. As with the note about garbage collection, that tends to cause a lot of page-in references going through the linked-list of memory blocks. I believe that there have been some improvements along the way, but don't know about them. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: Friday, August 7, 2015 5:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Limit number of frames of real storage per job Would'nt the garbage collection cause page-in references as objects are collected and co-located? Thus negatively affecting performance on page sensitive (e.g. CICS....) middleware/applications. Seems the advice to avoid garbage collection is sound to me (from a performance perspective). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
