zero filled page faults is an application behavior (e.g., malloc). Very little a system administrator can do.

File caching is automatic with AIX. Starting with AIX 6.1 the defaults for file caching behavior are pretty to very good.

Code:

              8388608 memory pages
              8058736 lruable pages
              2428935 free pages

24/84 % memory free
80/94 % memory demand pageable (least recently used "able")

Code:

              1404618 pinned pages
               384661 file pages
               384661 client pages
                 66.5 percentage of memory used for computational pages

4/84 % file caching (client == jfs2 files, files = jfs + jfs2, so (nearly) all files are jfs2
14/84 % memory pinned
computational memory is all working memory (application memory, plus program code (text))

Code:

                    5 pending disk I/Os blocked with no pbuf
                    0 paging space I/Os blocked with no psbuf
                 2228 filesystem I/Os blocked with no fsbuf
                 1537 client filesystem I/Os blocked with no fsbuf
                 4155 external pager filesystem I/Os blocked with no fsbuf

Above tells me:
* little raw disk i/o being done and/or sufficient buffers
* no paging space activity
* some jfs activity, and initial fs buffers could be tuned to higher number
* some real nfs/cd/dvd activity needing more buffers
* same for jfs2
In short, file system buffering should be checked.

ioo -a
nfso -a

commands will list the tunable variables.