title: JVM tuning on Amazon EC2
body: <p>We will be deploying a production application to Amazon EC2 very shortly.  Initially, we'll just be using a "small" instance, but have plans to scale up not long afterwards.  My question is, has any investigation been done on JVM tuning for the EC2 environment?  Are there any specific changes that we should make to our JVM parameters to compensate for quirks/characteristics of Amazon EC2?  Or, do the normal tuning methodologies apply here as they would in a physical environment?</p>
  
  <p>Our application will be deployed on Tomcat 6.x.  It is built using JBoss Seam 2.2.x, and uses PostgreSQL 8.x as the backend database.  Any advice you can give is greatly appreciated!</p>