Server configuration options
There are a number of server configurations that can affect
performance significantly.
To open the Server editor, double-click the server instance in the Servers view ().
Most of the items in the server configuration are set to give you the best performance, by default, with the exception of Publishing and Enable universal test client. If you do not require the universal test client, clear the checkbox to disable it.
It is recommended to set the publishing option to Never
publish automatically. Many of the changes that you make
to your projects and resources do not need to be published automatically.
Changes to HTML or JSP files are detected by the server but do not
need to be automatically published. Changes to servlets are detected
as part of the automatic servlet reloading function of the server.
It is recommend that you run the server in debug mode to use the JVM
support for hot method replace. With hot method replace, Java™ changes are injected into the running server.
Note: Some
class changes cannot be injected using the hot method replace function
due to the size or shape of the class change. In the case where a
class change cannot be injected using hot method replace, an informational
message will display after you save the file.
Select Optimize server for testing and developing to set the JVM parameters that improve the startup time of the server.
Tip: You can automatically scan for performance tuning
suggestions for your WebSphere Application Server configuration settings.
To access the workspace performance tuning tool, click .