Performance Tuning for Oracle WebCenter Content 11g - Fishbowl ...
Performance Tuning for Oracle WebCenter Content 11g - Fishbowl ...
Performance Tuning for Oracle WebCenter Content 11g - Fishbowl ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
-verbose:gc<br />
-XX:+PrintGCDetails<br />
-XX:+PrintGCTimeStamps<br />
-XX:NewRatio=4<br />
-Xnoclassgc<br />
-Xloggc:<br />
-Dweblogic.threadpool.MinPoolSize=72<br />
-Dweblogic.threadpool.MaxPoolSize=72<br />
-Dweblogic.SocketReaders=12cketReaders=12<br />
-Djps.auth.debug=false<br />
Operating system architecture does not on its own provide enough in<strong>for</strong>mation to properly<br />
tune the <strong>Content</strong> Server.<br />
As seen in the above example, repeated tuning and testing was required to find an optimum configuration. The<br />
content repository has the additional complexity of requiring different per<strong>for</strong>mance configurations <strong>for</strong> contribution<br />
and consumption environments. A heavy ingestion pattern will benefited from a -XgcPrio:throughput garbage<br />
collection, while searching may benefited from other GC models.<br />
Confirm your capitalization is correct. In many cases, command-line options are case sensitive unless explicitly<br />
stated. A configuration flag improperly set may be ignored, or cause unintended consequences.<br />
Disk<br />
Usage<br />
<strong>WebCenter</strong> <strong>Content</strong>, like the earlier versions of the content repository, has a variety of disk mounting options, with<br />
implications <strong>for</strong> what type of storage may be appropriate <strong>for</strong> each area. Directories within the content repository<br />
may have different service level agreements and per<strong>for</strong>mance requirements. Using a single storage system does<br />
not produce optimal per<strong>for</strong>mance-cost cost optimization.<br />
The latest incarnation of the <strong>Oracle</strong> <strong>Content</strong> Repository, a shared file system is still required <strong>for</strong> clustering. The<br />
ECM services run as Java processes. Prior to <strong>11g</strong>, these services took the strategy of keeping a memory cache,<br />
writing to a shared file system or database, and having the other nodes update their local cache. All content<br />
management services continue to be stateless and utilize the same concurrency mechanism even though they are<br />
living in a Java Enterprise Edition world.<br />
© 2012. <strong>Fishbowl</strong> Solutions, Inc.