HP-UX Programmer's Guide for Java 2
Table Of Contents
- Table of Contents
- 1 Introduction
- 2 HotSpot Technology Tools and Commands
- 3 Configuration for Java™ Support
- 4 Performance and Tuning
- 5 Measuring System Performance
- 6 Using Threads
- 7 Using Signals
- 8 Using Java™ 2 JNI on HP-UX
- 9 Expanding Memory
- Determine your requirements
- Memory layout under HP-UX 11.0 (PA-RISC only)
- Additional memory available under HP-UX 11i (PA-RISC only)
- Allocating physical memory and swap in the Java™ heap
- Useful key command-line options for allocating memory
- Application-dependent considerations using large heap size HP-UX 11i PA-RISC
- Expanding heap size in native applications on PA-RISC HP-UX 11.11 and later releases
- Expanding heap size in native applications on Integrity HP-UX 11.23 and later releases
- Expanding heap size in HP-UX PA-RISC
- Expanding heap size in HP-UX Integrity
- 10 Diagnosing Memory Leaks
- A JDK/JRE 6.0.n and 7.0.n Usage Notes
- Using Java 2 JNI on HP-UX
- Garbage collection
- Asian TrueType fonts and Asian locales
- Date/Time methods defaults
- Profiling
- Compatibility with previous releases
- Java Cryptography Extension (JCE) policy files
- Configuring the Java Runtime Plug-In
- CLASSPATH environment variable
- Java Web Start technology usage
- Upgrading from a previous Java Web Start version
- IPv6 support
- Allocation Site Statistics and Zero Preparation -Xverbosegc
- JDK 6.0.04 flags
- GC log-rotation support
- NUMA collector enhancements
- ThreadDumpPath support
- Garbage-First garbage collector (-XX:+UseG1GC)
- jmap, jinfo, and jstack tools included in JDK 6.0.03
- Additional Java Web Start documentation
- B JDK/JRE 5.0.n Usage Notes
- Using Java 2 JNI on HP-UX
- Garbage collectors: Parallel and Concurrent Mark Sweep
- Allocating physical memory and swap in the Java heap
- Asian TrueType fonts and Asian locales
- Date/Time methods defaults
- Profiling
- Closing a socket (PA-RISC only)
- Compatibility with previous releases
- Java Cryptography Extension (JCE) policy files
- Allocation Site Statistics and Zero Preparation -Xverbosegc
- IPv6 support on Java 5.0
- GC log-rotation support in 5.0
- ThreadDumpPath support in 5.0
- Dynamically loaded libraries in 5.0
- Performance improvement for String.intern()
- Configuring the Java Runtime Plug-In
- CLASSPATH environment variable
- Java Web Start technology usage
- C SDK/RTE 1.4.2.n Usage Notes
- Removing support for unwanted architectures in the JRE
- Support for dynamic thread local storage (TLS)
- Signal Chaining functionality
- Using Java 2 JNI on HP-UX
- HotSpot JVM options
- Garbage collectors: Parallel and Concurrent mark sweep
- Allocating physical memory and swap in the Java heap
- Asian TrueType fonts and Asian locales
- Date/Time methods defaults
- Profiling
- Closing a socket when accept or read is pending (PA-RISC) - new patch information!
- Compatibility with previous releases
- Runtime Plug-In usage and configuration
- GC log-rotation support
- ThreadDumpPath support
- D Additional Resources
- Index
-XX:PrefetchScanIntervalInBytes=n
Prefetch n bytes ahead for scavenge scan area. The default is 0. The ideal value may
vary depending on the processor.
-XX:+PrefetchScavengeFieldsAhead=n
Prefetch the next n fields of objects during scavenge. The default is 0. The ideal value
may vary depending on the processor.
-XX:+PrefetchMarkSweep
Use prefetching during full garbage collections. The default is true.
-XX:SchedulerPriorityRange=SCHED
This option can be used to both select the scheduling policy and map the Java™ thread
priorities, 1 (low) through 10 (high), to the underlying HP-UX thread priorities:
SCHED* is one of the scheduling policies:
SCHED_FIFO
SCHED_RR
SCHED_RR2
SCHED_RTPRIO
SCHED_OTHER
SCHED_HPUX
SCHED_NOAGE (a subset of the range of priorities supported by CHED_TI MESHARE)
SCHED_TIMESHARE is not supported as an option, but is the same
as SCHED_HPUX and use of any such non-supported
SCHED* will result in using the default policy,
SCHED_HPUX.
base - the HP-UX minimum value for the set of priorities to be mapped
top - the HP-UX maximum value for the set of priorities to be mapped
The format can be:
-XX:SchedulerPriorityRange<scheduler>,<base>,<top>
or <scheduler>
or <scheduler>,<base>
or <scheduler>,,<top>
Normally, the underlying system interfaces allow you to obtain the max and
min priorities:
sched_get_priority_max()
sched_get_priority_min()
Standard and non-standard options 25