Re: Check your ancient performance settings

Hello Vernon,

To reply to your assumption about activity level, here is the documentation from IBM, where activity level is an attribute of a pool definition in a subsystem definition

Thanks for pointing out. I'll re-read about that in the Work Management documentation. I must admit that my understanding of how pools, subsystems and job queues relate and provide an environment for "work" to be done could use some extending. :-)

Just a quick thought - the concept of single-level storage makes the IBM i quite different from Linux, etc., so things you know from Linux might lead you astray.

I've read some books from Frank Soltis about the underlying concepts. At first, I struggled to map IBM technobabble to Linux technobabble, but after actually experimenting and using the system for years, I guess I have a solid grip on most (but not all) stuff what's going on. :-)

Subsystems, Job Queues and Memory Pools are completely unknown on Linux or other unices. Paging, swapping, memory mapping, memory scarcity and resulting thrashing are known on both platforms. I still have the impression that with sufficient RAM, paging will cease to an unavoidable minimum, since there always can be some access to (part of) an object not in RAM yet; while most of the often used objects and files are already in RAM and will not get purged as long as there is, well, sufficient RAM available.

:wq! PoC

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