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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Shared class cache<br />

This section contains special information about the shared class cache usage on<br />

z/OS.<br />

Overview<br />

The shared class cache is used to share <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> and<br />

user classes between multiple JVMs.<br />

JVMs that use the shared class cache start up more quickly, and have lower<br />

storage requirements than JVMs that do not. The overall cost of class loading is<br />

also reduced when JVMs use the shared class cache. When a new JVM that<br />

shares the class cache is initialized, it uses the preloaded classes instead of<br />

reading them from the file system. A JVM that shares the class cache still owns<br />

all the working data (objects and variables) for the applications that run in it. This<br />

helps to maintain the isolation between the Java applications being processed in<br />

the system.<br />

The first JVM, after an IPL or after the cache has been destroyed, will take<br />

between 0–5% longer, to fill the cache. The startup time of subsequent JVMs will<br />

decrease by 10–40%, depending on the number of classes being loaded.<br />

The z/OS implementation links pages in the private area of the address space<br />

that uses the cache to the frames of the original location of the cache. Because<br />

shared memory is used, BPXPRMxx parmlib settings affect the cache<br />

performance.<br />

Important settings<br />

Consider these factors when using shared class cache in your environment:<br />

► Cache size limits<br />

The maximum theoretical cache size is 2 GB. The size of cache you can<br />

specify is limited by the amount of physical memory and swap space available<br />

to the system. The cache for sharing classes is allocated using the System V<br />

IPC Shared memory mechanism. Because the virtual address space of a<br />

process is shared between the shared classes cache and the Java heap, if<br />

you increase the maximum size of the Java heap you might reduce the size of<br />

the shared classes cache you can create.<br />

► BPXPRMxx settings for shared memory<br />

The following settings affect the amount of shared memory pages available to<br />

the JVM.<br />

– MAXSHAREPAGES<br />

– IPCSHMSPAGES<br />

– IPCSHMMPAGES<br />

– IPCSHMMSEGS<br />

470 <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!