- Initial Heap Size : 64MB
- Max Heap Size: 1024MB
What does this mean? It means that if you deploy a VM w/ 8GB of RAM to install VSC on, it will only EVER use 1GB of RAM. The VSC (4.2.2) also tends to have performance issues when dealing w/ larger environments. There is an article somewhere, but I can't find it for the life of me right now. Anyway to fix this issue, you need to modify the wrapper.conf file.
This is typically in the installation directory of C:\Program Files\NetApp\Virtual Storage Console\wrapper\wrapper.conf
The lines you need to modify are:
# Initial Java Heap Size (in MB)
# Maximum Java Heap Size (in MB)
Now you 'can' up the heap to 4GB max if you think it needs it, but I'd recommend looking @ "Active Memory" stats of the VM this VSC runs on to make sure it 'actually' needs that much. I found in my environment (2000+ VM's), I didn't need to go above this number since it never breached more than 3.5GB. Since it was staying steady around 3GB, I decided to change the initial heap to 3GB so it wouldn't have to keep building it up on startup.
Later version of VSC 'might' not have this same issue, but you can this same logic if it does.
You may need to apply this to the NetApp SnapManager Service as well, that is located in:
C:\Program Files\NetApp\Virtual Storage Console\smvi\server\etc\wrapper.conf