Zone capped-memory

 We have a server with 64 GB Memory.

root@reg-glb12 # swap -s

total: 8562200k bytes allocated + 8065888k reserved = 16628088k used, 60748712k available

root@reg-glb12 # swap -l

swapfile             dev  swaplo blocks   free

/dev/zvol/dsk/rpool/swap 256,1      16 134217712 134217712

We created a container with 16G memory & 32 G Swap cap

root@reg-glb12# zonecfg -z <zonename> info

......

.....

capped-memory:

        physical: 16G

        [swap: 32G]

......

Whereas inside the zone, it is showing as

root@reg-xxx# swap -l

swapfile             dev  swaplo blocks   free

/dev/swap           4294967295,4294967295     16 67108864 66315968

root@reg-xxx# swap -s

total: 396448k bytes allocated + 0k reserved = 396448k used, 33157984k available

Application team complaining that the performance is very very slow. Can someone help to understand is the capping done correctly. Why 0k is reserved inside the container.