Differences between revisions 4 and 5
Revision 4 as of 2016-02-02 15:55:47
Size: 1084
Editor: Nick Hayward
Comment:
Revision 5 as of 2016-02-02 15:58:22
Size: 1085
Editor: wilhelms
Comment: Fixed typo
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 * Turn off auto-deploy in production (Tomcat). Deploy on start up will still be enabled. With auto-deply enabled every few minutes your application server will scan all of the application directories. Depending on how large they are or how many small files you have that can make a difference especially over a networked file system.  * Turn off auto-deploy in production (Tomcat). Deploy on start up will still be enabled. With auto-deploy enabled every few minutes your application server will scan all of the application directories. Depending on how large they are or how many small files you have that can make a difference especially over a networked file system.
Line 6: Line 6:
 * A lot of folks with dedicated solutions run behind something like Apache when they don't need to. If your application is all Java then you probably don't need it and the proxy pass can cost you 20ms per request. **note use jsvc, or tcp proxy to avoid running as root if your application server does not drop privilages.  * A lot of folks with dedicated solutions run behind something like Apache when they don't need to. If your application is all Java then you probably don't need it and the proxy pass can cost you 20ms per request. **note use jsvc, or tcp proxy to avoid running as root if your application server does not drop privileges.

Performance considerations / Performance tuning your JVM, Tomcat, Jboss

Things come pretty well optimized, and we try and start with heap sizes and settings that are appropriate. Some things to take a look at to increase your performance:

  • Turn off auto-deploy in production (Tomcat). Deploy on start up will still be enabled. With auto-deploy enabled every few minutes your application server will scan all of the application directories. Depending on how large they are or how many small files you have that can make a difference especially over a networked file system.
  • Turn off debug level logging in production. This is true of any of the Java application servers but particularly so with many version of Jboss.
  • A lot of folks with dedicated solutions run behind something like Apache when they don't need to. If your application is all Java then you probably don't need it and the proxy pass can cost you 20ms per request. **note use jsvc, or tcp proxy to avoid running as root if your application server does not drop privileges.


CategoryJava

Java/performance (last edited 2016-02-02 16:12:54 by wilhelms)