29.01.2013 Views

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4.5.5 Production system tuning<br />

This is where you apply all the performance, scalability, and high availability<br />

considerations in production. Tuning the system is an iterative process that<br />

involves optimizing <strong>WebSphere</strong> parameters to suit your runtime environment.<br />

Important: To perform tuning in the production environment, have the final<br />

version of code running. This version should have passed performance tests<br />

on the integration environment prior to changing any <strong>WebSphere</strong> parameters<br />

on the production system.<br />

When changing a production environment, use some standard practices:<br />

► Change only one parameter at a time.<br />

► Document all changes.<br />

► Compare several test runs to the baseline.<br />

Changes between test runs should not differ by more than a small percentage to<br />

preclude introducing new problems that you might need to sort out before you<br />

continue tuning.<br />

As soon as you finish tuning your production systems, apply the settings to your<br />

test environments to make sure that they are similar to production. Plan to rerun<br />

your tests there to establish new baselines on these systems and to see how<br />

these changes affect the performance.<br />

Keep in mind that you often only have one chance to get this right. Normally, as<br />

soon as you are in production with your system, you cannot run performance<br />

tests on this environment any more, simply because you cannot take the<br />

production system offline to run more performance tests. If a production system<br />

is being tested, it is likely that the system is running in a severely degraded<br />

position, and you have already lost half the battle.<br />

Note: Because it is rare to use a production system for load tests, it is usually<br />

a bad idea to migrate these environments to new <strong>WebSphere</strong> versions without<br />

doing a proper test on an equivalent test system or new hardware.<br />

After completing your first performance tests and tuning the <strong>WebSphere</strong><br />

parameters, evaluate your results and compare them to your objectives to see<br />

how all of this worked out for you.<br />

112 <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> <strong>V7.0</strong>: <strong>Concepts</strong>, Planning, and Design

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!