Re: Breaking up one partition into two.

Rob,

Points taken, however any user process running in *BASE (meaning any non-IBM process) will slow the entire system down since that's were many of the IBM i processes get their memory (host servers come to mind right away). When the system has to fight user jobs for resources everyone looses. Paging at over 5400 in non-database *BASE is way outside of any guideline I've ever seen.

Response times may be OK since there is so much horsepower that the system can bulldoze its way through the thrashing, but I'll bet there is latent demand that is not serviced as fast as it should be when loads start to climb a bit.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 7/22/2011 3:22 PM, rob@xxxxxxxxx wrote:

We do already have separate IP addresses for each domino server and a
separate one for i, (and another separate one with it's own card for
Mimix).

Back in the day we used to manage memory ourselves. We used to have two
job schedule entries NIGHT and DAY that would shift memory between batch
and interactive. We kind of like this theory of autonomics and having the
system fix itself.

Our concern with creating multiple pools is that you end up allocating
resources that are not available to other processes. For example, if I
bust *BASE into *BASE and DOMINO. I would allocate x memory to *BASE and
y memory to DOMINO. If one is not using it and the other is not (and
QPFRADJ is turned off) then I end up with a bunch of inventory not being
used, when other processes would love to have it.

I think one theory is that by busting out DOMINO from *BASE you can
control a spike in either from affecting the other. Is there some other
reason to do so? Like, "paging option"? I heard someone mention run
priority. I thought that was something at the job level. Upon further
review I do see that subsystems support "classes". From there you can
control run priority, time slices, threads, etc. I guess I just don't
know enough "why" as to why I would want to do this other work. Like
restricting down threads, etc.

In general "I thought" our performance was good. Throwing money at a
problem greatly simplifies management. There's a lot that I used to do on
AS/400's that I don't mess with so much anymore on Power equipment. Also,
our people thrive on Domino. If I throttled down a hundred Domino users
so one persons A/P check run would have priority it would not go over
well.

I have forgotton so much, like why faulting is bad, but even more so, the
guidelines as to what levels constitute high faulting. I can't believe
the number one used on a B10 is applicable to a 9117-MMA.

I am seeing that a separate partition for this is probably a bad idea. But
I am still trying the grasp why a separate pool might help.


Rob Berendt
-- Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com