2,187
edits
Difference between revisions of "Configuration (vCentre)"
Jump to navigation
Jump to search
Configuration (vCentre) (view source)
Revision as of 22:32, 17 January 2013
, 22:32, 17 January 2013→TomCat Memory Throttle: Added vSphere 5
(Initial creation - content from vCentre page) |
(→TomCat Memory Throttle: Added vSphere 5) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 52: | Line 52: | ||
== TomCat Memory Throttle == | == TomCat Memory Throttle == | ||
The Tomcat webserver (used to provide VC Web-services), can be very memory hungry (up to 1GB) in comparison to when it ran on VC v2.5 (normally around 50MB). This can be throttled down, though this is only recommended for small, non-production installations (<10 ESX's). Bear in mind that things like [[Acronyms#A|API]] access (inc [[:Category:PowerCLI|PowerCLI) are serviced by the VMware vCentre WebServices, so if these become sluggish you may need to increase. For home lab, single ESX installations you can reduce down to 64 MB. | '''None of the changes in this section are suitable for production environments''' | ||
=== vSphere 4 === | |||
The Tomcat webserver (used to provide VC Web-services), can be very memory hungry (up to 1GB) in comparison to when it ran on VC v2.5 (normally around 50MB). This can be throttled down, though this is only recommended for small, non-production installations (<10 ESX's). Bear in mind that things like [[Acronyms#A|API]] access (inc [[:Category:PowerCLI|PowerCLI]]) are serviced by the VMware vCentre WebServices, so if these become sluggish you may need to increase. For home lab, single ESX installations you can reduce down to 64 MB. | |||
# Edit the registry to put a ceiling on the Java VM's memory usage | # Edit the registry to put a ceiling on the Java VM's memory usage | ||
| Line 58: | Line 61: | ||
# Restart the service | # Restart the service | ||
#* <code> VMware VirtualCenter Management Webservices </code> | #* <code> VMware VirtualCenter Management Webservices </code> | ||
=== vSphere 5 === | |||
Java is now used for the following... | |||
* VirtualCenter Management Webservices | |||
* Inventory Service | |||
* Profile-Driven Storage Service | |||
* Single Sign On | |||
...and in their default configuration makes vCentre a bit memory hungry for a small test/home environment. Throttle down by the following procedure (not to be used for production installations). | |||
# Edit <code>.\VMware\Infrastructure\tomcat\conf\wrapper.conf</code> | |||
#* Update the line <code>wrapper.java.additional.9="-Xmx512M"</code> | |||
# Edit <code>.\VMware\Infrastructure\SSOServer\conf\wrapper.conf</code> | |||
#* Update the line <code>wrapper.java.additional.9="-Xmx512M"</code> | |||
# Edit <code>.VMware\Infrastructure\Inventory Service\conf\wrapper.conf</code> | |||
#* Update the line <code>wrapper.java.initmemory=128</code> | |||
#* Update the line <code>wrapper.java.maxmemory=512</code> | |||
# Edit <code>.\Infrastructure\Profile-Driven Storage\conf\wrapper.conf</code> | |||
#* Update the line <code>wrapper.java.initmemory=128</code> | |||
#* Update the line <code>wrapper.java.maxmemory=512</code> | |||
# Restart the server to apply the changes | |||
Start Notepad as an administrator if you have trouble saving changes | |||
The above was adapted from http://defaultreasoning.com/2012/09/27/tweaking-java-exe-memory-usage-on-vcenter-server-5-1/ | |||
== ESX Poll Time-out == | == ESX Poll Time-out == | ||