We are a small shop with 150MB of ECSA that is 50% allocated. We have roughly 200 asids. From my experience any one asid using more than 5MB is highly suspect. That is a big block of memory, if you can't do it with that then you're probably doing it incorrectly. I'm not sure that pageable vs non-pageable matters, it certainly doesn't to me. Either comes out of my ECSA total and when that total is exhausted, I'm in trouble. Hence the 50% allocated to give some time to find and prosecute the offender(s). Nowadays, it is usually a creep (memory leak) more than a sudden allocation. I just checked who has what amount ECSA allocated and, other than DB2, all are less than 1MB most are less than 500K. I hope this helps you. Cliff McNeill
> Date: Mon, 30 Jun 2014 13:34:37 -0700 > From: [email protected] > Subject: Re: ECSA Survey > To: [email protected] > > Thanks a lot for hijacking my thread, guys. <g> > > Is there however not one active sysprog out there willing to say "we have ___ > MB of ECSA serving about ____ address spaces, and frankly, I think ____KB/MB > would be a borderline unreasonable amount of pageable ECSA for a vendor > product to require"? > > Charles > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
