2,187
edits
Difference between revisions of "Configuration (vCentre)"
Jump to navigation
Jump to search
m
Configuration (vCentre) (view source)
Revision as of 21:30, 17 January 2013
, 21:30, 17 January 2013→TomCat Memory Throttle: Fix typo
m (Sstrutt moved page Configuration (Virtual Centre) to Configuration (vCentre) without leaving a redirect: Incorrect title) |
m (→TomCat Memory Throttle: Fix typo) |
||
| 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. | 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 | ||