An LPAR has 32 CPUs, and is reporting hundreds of page-ins and page-outs per second. At what level of paging should the administrator become concerned?

Paging space size in 4KB pages is a capacity metric, not a performance rate threshold, and has no defined relationship to when paging rates become problematic.

A flat 50 pages per second ignores CPU count entirely, making it meaninglessly restrictive for large LPARs and too permissive for small ones.

IBM AIX performance guidelines define the paging concern threshold as 10 pages per CPU per second, which scales the threshold proportionally to the system's processing capacity. For this 32-CPU LPAR, that yields a 320 pages-per-second threshold, providing a CPU-relative baseline that accounts for the system's workload capacity rather than an arbitrary fixed number.

IBM's paging concern guideline is CPU-relative, not memory-relative; allocated memory size is not the scaling factor used in AIX performance tuning standards.

The number of paging space disks is a storage configuration value that affects throughput capacity, not a defined rate threshold for performance concern.