Skip to main content

Java HotSpot VM Settings



The following JVM parameters are recommended:

-Djava.awt.headless=true 
-Dfile.encoding=UTF-8 
-server 
-Xms512m 
-Xmx1024m 
-XX:NewSize=256m 
-XX:MaxNewSize=256m 
-XX:PermSize=256m 
-XX:MaxPermSize=256m 
-XX:+DisableExplicitGC

-Djava.awt.headless=true
  • Headless mode is a system configuration in which the display device, keyboard, or mouse is lacking. Sounds unexpected, but actually you can perform different operations in this mode, even with graphic data.
-server
  • The JDK includes two flavors of the VM -- a client-side offering, and a VM tuned for server applications. These two solutions share the Java HotSpot runtime environment code base, but use different compilers that are suited to the distinctly unique performance characteristics of clients and servers. These differences include the compilation inlining policy and heap defaults. Although the Server and the Client VMs are similar, the Server VM has been specially tuned to maximize peak operating speed. It is intended for executing long-running server applications, which need the fastest possible operating speed more than a fast start-up time or smaller runtime memory footprint. 
-Dfile.encoding=UTF-8  
  • Tell the JVM to use UTF-8 as an encoding for text files to be more platform independent
-Xms512m
  • Set the initial Java Heap memory size to 512 Megabytes
-Xmx1024m
  • Set the maximal Java Heap memory size to 1024 Megabytes
-XX:NewSize=256m
  • Set the default size of new generation to 256 Megabytes
-XX:MaxNewSize=256m
  • Set the default maximum size of new generation to 256 Megabytes
-XX:PermSize=64m
  • Set the initial HotSpot PermGen Memory size to 64 Megabytes
-XX:MaxPermSize=256m
  • Set the maximum PermGen size to 256 Megabytes. This is especially recommended when redeploying Fedora 4 often, since otherwise OutOfMemory in the PermGen space errors will occur.
-XX:+DisableExplicitGC
  •  Disable calls to System.gc(), JVM still performs garbage collection when necessary.

Labels:

Comments

Post a Comment

Popular posts from this blog

Configure Tomcat Web Management Interface

We already see, how to install tomcat in ubuntu in my previous blog( http://kmlsarwar.blogspot.com/2014/08/how-to-install-apache-tomcat-on-ubuntu.html ) In order to use the manager webapp installed, we must add a login to our Tomcat server. We will do this by editing the tomcat-users.xml file: sudo nano /etc/tomcat7/tomcat-users.xml    This file is filled with comments which describe how to configure the file. You may want to delete all the comments between the following two lines, or you may leave them if you want to reference the examples: <tomcat-users> </tomcat-users>  You will want to add a user who can access the manager-gui and admin-gui (the management interface that we installed in Step Three). You can do so by defining a user similar to the example below. Be sure to change the password and username if you wish: <tomcat-users> <user username="admin" password="password" roles="manager-gui,admin-gui"...
Post a Comment
Read more

How to install Oracle JDK on Ubuntu from repository

This package provides Oracle Java JDK 7 (which includes Java JDK, JRE and the Java browser plugin). However, you can't only install Oracle JRE - the PPA only provides the full Oracle JDK7 package. To install: sudo add-apt-repository ppa:webupd8team/java sudo apt-get update sudo apt-get install oracle-jdk7-installer And to uninstall: sudo apt-get remove oracle-jdk7-installer And to verify your installation: java -version java version "1.7.0_51" Java(TM) SE Runtime Environment (build 1.7.0_51-b13) Java HotSpot(TM) 64-Bit Server VM (build 22.0-b10, mixed mode) And to verify the web browser installation: http://java.com/en/download/installed.jsp Verified Java Version Congratulations! You have the recommended Java installed (1.7.0_51). And to update: If for some reason, the Java version in use is not 1.7.0, you can try to run the following command: sudo update-java-alternatives -s java-7-oracle To Install and Set in environment variable: To...
Post a Comment
Read more

JavaMelody: Monitoring the Performance of Tomcat Application Server

Javamelody is an opensource (LGPL) application to monitor Java or Java EE application servers in QA and production environments. JavaMelody is mainly based on statistics of requests and on evolution charts. (Extract from the Javamelody home page) It allows to improve applications in QA and production Give facts about the average response times and number of executions Make decisions when trends are bad, before problems become too serious Optimize based on the more limiting response times Find the root causes of response times Verify the real improvement after optimization It includes summary charts showing the evolution over time of the following indicators: Number of executions, mean execution times and percentage of errors of http requests, sql requests, jsp pages or methods of business façades (if EJB3, Spring or Guice) Java memory Java CPU Number of user sessions Number of jdbc connections These charts can be viewed on the current day, week, month, year or cu...
Post a Comment
Read more