1. Create an OpenShift on Power Cluster 4.16 on...
2. Create a worker-optimize MachineConfigPool
3. Create a Performance Profile
```
apiVersion: performance.openshift.io/v2
kind: PerformanceProfile
metadata:
finalizers:

• foreground-deletion
  name: optimize
  spec:
  additionalKernelArgs:
• idle=poll
  cpu:
  isolated: 0,3
  reserved: 1-2
  globallyDisableIrqLoadBalancing: true
  hugepages:
  defaultHugepagesSize: "4K"
  pages:
• size: "1G"
  node: 0
  count: 1
  nodeSelector:
  node-role.kubernetes.io/worker-optimize: ""
  numa:
  topologyPolicy: restricted
  realTimeKernel:
  enabled: false
  ```

IBM Power supports `ppc64 supports 4K and 16M` page sizes https://www.kernel.org/doc/html/v5.9/admin-guide/mm/hugetlbpage.html Huge PageSize is 16M and 16G

```
Warning: metadata.finalizers: "foreground-deletion": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers
The PerformanceProfile "optimize" is invalid:

• spec.nodeSelector: Invalid value: map[string]string {"node-role.kubernetes.io/":""}

  : key: Invalid value: "node-role.kubernetes.io/": name part must be non-empty; name part must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName', or 'my.name', or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]')

• spec.hugepages.defaultHugepagesSize: Invalid value: "4k": The compatible default huge page sizes for the selected kernel page size 4k are: map[16G:{} 1G:{} 2M:{} 32M:{} 512M:{} 64k:{}]. doc reference=https://docs.kernel.org/mm/vmemmap_dedup.html
  node/worker2.xyz123.cp.fyre.ibm.com unlabeled
  ```