Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Performance Tuning Guide

- Previous: HTTP Session Handling
- Next: EJB Performance Tuning

### Configuration and Deployment Tips

Follow these configuration tips to improve performance. These tips are intended for production environments, not development environments.

- To improve class loading time, avoid having excessive directories in the server `CLASSPATH`. Put application-related classes into JAR files.

- HTTP response times are dependent on how the keep-alive subsystem and the HTTP server is tuned in general. For more information, see HTTP Service Settings

- If you are using Solaris 8, optimize SSL by using the `mtmalloc` library that provides a collection of `malloc` routines for concurrent access to heap space. To use `mtmalloc`:

  - Get patch 111308-03 from SunSolve Onlineand install it.

  - Edit the `startserv` script located in `bin/startserv` for your domain, and define the LD_PRELOAD environment variable to be `/usr/lib/libmtmalloc.so`.

    The exact syntax to define an environment variable depends on the shell you use.

- Cache servlet results when possible. For more information, see Chapter 5, Developing Web Applications, in Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Developer’s Guide.

- If an application does not contain any EJB components, deploy the application as a WAR file, not an EAR file.

#### Disable Security Manager

The security manager is expensive because calls to required resources must call the `doPrivileged()` method and must also check the resource with the `server.policy` file. If you are sure that no malicious code will be run on the server and you do not use authentication within your application, then you can disable the security manager.

To disable use of the `server.policy` file, use the Admin Console. Under Configurations > config-name > JVM Settings (JVM Options) delete the option that looks like this:

    -Djava.security.policy=${com.sun.aas.instanceRoot}/config/server.policy

- Previous: HTTP Session Handling
- Next: EJB Performance Tuning

- © 2010, Oracle Corporation and/or its affiliates