Is there a best practice on how much memory we should allocate service console.
Also is there any tools we can check how much memory is being used by the service console and if we need to allocate more.
do you use any 3rd part software inside your service console? Like backup agents or ups software?
How many vcpu manages your single host?
The minimum set in the installation process is sufficient for most of enviroments BUT check it with top command.
If you have 50-60 vcpu in your esx host, take memory up to 512 <-- See that you need a reboot to apply this change
The maximum amount of memory you can assign to SC is 800MB ... Just incase ...
For monitoring you can maybe check out veeam software .... They have some great tools.. That is, if you want to go the Third party way of course.
from a personal perspective, I always create my SC with 800Mb,
One important thing remember, is that you need to set your swap partition to at least 1600 MB during installation. as it will save you a lot of pain later on if you do decide to increase the memory needed
If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points
Tom Howarth
VMware Communities User Moderator
Blog: www.planetvm.net
Is there a command I can use on the service console to check what the swap partition is set to currently
Something like "more /proc/meminfo" on the cli would do the trick I think ...
In my VMware VCP class they told us just to allocate the 800 MB -- that way you never have to worry about increasing or running out later.
All of my ESX servers have their service console configured for 800 MB. Most of my ESX boxes have 32 or 64 GB of RAM anyways, I'd rather allocate the 1 GB to the SC and not have to worry about not having enough for it later.
free command from the root, should do the trick, For further, understanding, please refer to the following post
http://communities.vmware.com/message/477089;jsessionid=3275A231675C48EBB0E38B08B767E2BB
Please reward points, if this answer helps you.