Largest LPARs we have are about 200GB with 6 MOD27 per LPAR. They all run DB2 for distributed workloads plus some application specific subsystems. The two busiest of those LPARs each run one DB2 member of the same DB2 data sharing group with a frame occupancy of about 39M. Next to no paging.
Bart -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Pinnacle Sent: Tuesday, April 11, 2017 10:47 AM To: [email protected] Subject: Paging subsystems in the era of bigass memory Gone are the halcyon days when we could run an LPAR with three mod-3's as the local paging subsystem. With today's large memory sizes, I'm faced with having to completely rethink my paging subsystems. I've currently got a 133GB LPAR with 18 mod-9 locals at 44%. I'm going to add 22 more mod-9's, which will get me just under the 30% threshold. That's 40 page datasets, which is about 30 more than the most I've ever managed. I'm thinking about going to 10 mod-54's as my final solution for this LPAR (roughly 4x the real memory). I wondered what the rest of you are doing with your paging subsystems in the era of bigass memory sizes. Regards, Tom Conley -- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
