Better performance in production servers is possible with proper configuration of JVM parameters, particularily those related to memory usage and garbage collection.

Server caching can speed dynamic pages to near-static speeds. Many pages created by database queries only change every 15 minutes or so, e.g. CNN or Slashdot. Resin can cache the results and serve them like static pages. Resin's caching will work for any servlet, including JSP and XTP pages. It depends only on the headers the servlet returns in the response.

By default, pages are not cached. To cache, a page must set a HTTP caching header.

Resin's caching operates like a proxy cache. It's controlled by the same HTTP headers as any proxy cache. Every user shares the same cached page.

A repository of notes and comments that will eventually make their way into the documentation. Please treat the information here with caution, it has often not been verified.