Re: Memory and CPU Considerations for IBM i LPARs

Patrik:

IBM i hosting allowing for the I/O of the Network Server Description to be
moved to a shared pool was delivered by IBM circa V7R2? (or thereabouts,
could be earlier). It allows the memory used to manage I/O for the server
into a specific shared memory pool so we can manage the memory usage and
performance of the system. See example command:

CRTNWSD NWSD(NEWONE) RSRCNAME(CMN??) POOL(*SHRPOOL50)

I usually use shared pool 50 and higher simply because it tends to not get
in the way of other shared memory pool assignments.
This is done with any IBM i hosting partition regardless if it's managed by
HMC or VPM.

To answer the original post, this allows the OP to manage how much memory
is used for I/O on each hosted environment, within the hosting system. CPU
and partition memory are managed (in this case) by the HMC.

I manage several systems using these techniques and I would argue they are
the current professional standard for anything but the smallest system.


--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Thu, Aug 22, 2024 at 10:41 AM Patrik Schindler <poc@xxxxxxxxxx> wrote:

Hello Jim,

Am 22.08.2024 um 16:42 schrieb Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx>:

If you have not moved the hosted environment into its own shared pool(s)

then all that work and the work the host does in *BASE is mixed and
interesting things can show up and hamper operations. I said "interesting"
because hosting certainly can stay in *BASE successfully, but it's not in
my view a best practice, unless that's the only thing IBM i does is host
the other environments.

Is your allegation based on current experience, or based on old and
probably outdated best practices when memory was scarce?

No offense intended, just asking clearly.

:wq! PoC

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.