Re: Check your ancient performance settings

I should have said QBASE - I just was not at a system, so I was trying to remember these things.

If you specify QBASE as your controlling subsystem, almost everything runs in pool 2. If you specify QCTL, several workloads run in their own fixed pool or in shared pools.

I will admit that one can over-manage work management - it can be more work than the ROI is worth.

But the recommendation to use QCTL instead of QBASE suggests to me that it is worth splitting some things into their own pools. I mentioned a couple examples, others on the list, such as Jim Oberholtzer, have given help on moving various workloads into their own pool - web serving is one example, where you don't want users to wait for on-system tasks to go through their work before the resources are available to the web or ODBC or other remote request.

Yes, things are faster, there is more space that runs better (SSDs), so I still think if that is all good, you can do even better where needed by separating workloads into separate pools.

Vern

On 10/9/2019 7:08 AM, Patrik Schindler wrote:

Hello Vern,

Am 08.10.2019 um 19:02 schrieb Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>:

Generally I agree with this - but there are workloads that can benefit from being in their own pool - things like ODBC or JDBC requests, web serving requests, etc.

If you leave those at default, they will probably be in *BASE or QCTL and contend for resources with all the stuff running there.

May I ask you to elaborate? As I wrote, today, RAM isn't a scarce resource anymore. CPUs are shared among all subsystems and pools, anyways. So, maybe you are referring to Disk-I/O?

Btw., *BASE is a pool and QCTL is a subsystem. What exactly do you mean by that?

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc