HP-UX Java性能优化指南（日文高清版）

需积分: 9 179 浏览量更新于2024-07-25 收藏 1017KB PDF 举报

"HP-UX Java性能调优白皮书（日文版）" 该资源是HP公司发布的一份关于在HP-UX（Hewlett-Packard UNIX）操作系统上进行Java性能调优的专业指南。这份文档详细阐述了如何在UNIX环境中优化Java应用程序的性能，以获得更高效、更稳定的表现。尽管是日文版，但对熟悉Java性能调优的专业人士来说，即使不精通日语，也可能通过技术术语和图表来理解其中的关键概念和步骤。在HP-UX上运行Java应用程序时，性能调优通常涉及以下几个核心方面： 1. **JVM参数调整**：Java虚拟机（JVM）的配置参数对性能有很大影响。这包括堆大小设置（如-Xms和-Xmx）、垃圾收集器的选择和配置、线程池大小等。调优这些参数可以确保JVM能够有效地管理内存，避免OutOfMemoryError，并减少垃圾收集的开销。 2. **类加载器优化**：理解类加载机制有助于避免类冲突和内存泄漏。调优类加载器的配置可以帮助提高应用启动速度和运行效率。 3. **代码优化**：通过分析和重构代码，消除不必要的计算和资源消耗，可以显著提升性能。这可能涉及到方法内联、减少对象创建、使用本地方法等。 4. **并发与多线程**：HP-UX支持多处理器和多核环境，因此理解和优化并发策略至关重要。这包括合理设置线程池大小、避免死锁和竞态条件、使用并发工具进行监控等。 5. **I/O优化**：在UNIX系统中，I/O操作的性能直接影响到应用的整体表现。这可能涉及到文件系统选择、缓冲策略、异步I/O的使用等。 6. **网络优化**：对于网络密集型应用，优化网络通信协议和连接池设置可以减少延迟并提高吞吐量。 7. **硬件适配**：HP-UX系统通常在Itanium处理器上运行，因此了解硬件特性并据此调整软件配置可以进一步提升性能。例如，利用硬件缓存、优化内存访问模式等。 8. **监控与诊断工具**：HP-UX提供了一系列性能监控工具，如HP Performance Advisor，用于跟踪和分析CPU、内存、I/O等资源的使用情况，帮助定位性能瓶颈。 9. **JDK版本选择**：选择适合业务需求的JDK版本也很关键。不同的JDK版本可能有不同的性能特性和优化策略。 10. **热部署与更新**：在生产环境中，无停机的更新和部署策略也能影响性能。理解如何在不影响服务的情况下更新应用和配置是调优的一部分。虽然这份白皮书是日文版，但对于有经验的IT专业人士来说，依然可以通过技术术语和图表来理解关键的调优策略。不过，对于非日语使用者，可能需要借助翻译工具或寻找英文版本的类似资源来获取更深入的理解。

foreground task until completed, regardless of how long the compilation takes. This

flag is provided for users who desire more deterministic behavior of method compilation

for purposes such as benchmarking.

-Xbootclasspath

Specify a semicolon-separated list of directories, JAR archives, and ZIP archives to

search for boot class files. These will be used in place of the default boot class files in

the jre/lib/rt.jar and jre/lib/i18n.jar archives normally used by the Java™

2 software.

-XdoCloseWithReadPending

The java command-line option -XdoCloseWithReadPending allows one thread to

close() a socket when there is an outstanding read pending on that same socket from

another thread.

For more information on when and how to use this option, see Closing a socket when

accept or read is pending (PA-RISC).

-Xeprof

The -Xeprof option generates profile data for HPjmeter. The -Xeprof option controls

profiling of Java™ applications running on JRE for HP-UX for the Java™ 2 Platform

and collects method clock and CPU times, method call count, and call graph.

NOTE: Zero preparation profiling is a beta feature of the HP JDK/JRE 5.0.03. It is

started from the command line by sending a signal to the JVM to start eprof. Engaging

zero preparation profiling may have a short term impact on application performance

as the JVM adjusts to the demands of performing dynamic measurements.

To profile your application, use the following command:

java -Xeprof:<options> ApplicationClassName

To profile your applet, use:

appletviewer -J-Xeprof:<options> URL

where <options> is a list of <key>[=<value>] arguments separated by commas.

We have found the following options useful in most cases:

For CPU time metrics with minimal intrusion:

-Xeprof

Exact call count information and object creation profiling:

-Xeprof:inlining=disable

To see the complete list of available options, use

java-Xeprof:help

16 HotSpot Technology Tools and Commands

When the -Xprep option is specified, before loading the application classes, the Java™

VM will load the specified factory class and execute the method in the class declared

as:

class <factory_class_name>

implements

Preprocessor {public static Preprocessor createPreprocessor

(String arg)

where Preprocessor is an interface defined as:

package hp.javatools.bytecode;

public interface Preprocessor {public abstract byte[] instrument\

(String name, byte[] klass);}

The VM will pass the <arguments> specified in the -Xprep option to the

createPreprocessor method as its only argument. The Preprocessor object returned

by the invocation will be saved by the VM.

For each subsequently loaded class, the VM will invoke the instrument() method

on the Preprocessor object, passing the name of the class being loaded, and the bytecode

representation of the class. The returned array of bytes will be used by the VM as the

replacement of the original version of the class. If null is returned, the original version

of the class will be used.

-Xprof

(excerpt below from http://java.sun.com/products/hotspot/2.0/README.html)

Profiles the running program, and sends profiling data to standard output. This option

is provided as a utility that is useful in program development and is not intended to

be used in production systems.

-Xrs (version 1.3.1 and later)

Reduces use of operating-system signals by the Java™ virtual machine (JVM), allowing

for orderly shutdown of a Java™ application. Using the -Xrs option removes the signal

handlers (for SIGHUP, SIGINT and SIGTERM) that run the shutdown hooks that are

used to shut the application down in an orderly fashion. If you use -Xrs, the shutdown

hooks will not be run if the application terminates as a result of receiving a SIGHUP,

SIGINT or SIGTERM signal, unless the your code explicitly catches these and runs the

shutdown hooks itself.

-Xshare:on, -Xshare:off, -Xshared:auto

UserSharedSpaces is not supported on HP-UX

-Xrunhprof

Enables cpu, heap, or monitor profiling. This option is typically followed by a list of

comma-separated "<suboption>=<value>" pairs. Run the command java

-Xrunhprof:help to obtain a list of suboptions and their default values.

-Xss<size>

Standard and non-standard options 19

(excerpt below from http://java.sun.com/j2se/1.3/docs/tooldocs/solaris/java.html#options)

Set the maximum native stack size, in bytes, for any thread. Each Java™ thread has

two stacks: one for Java™ code and one for C code. This option sets the maximum stack

size that can be used by C code in a thread. Every thread spawned during the execution

of the program passed to java will have the number you specify in this option as its C

stack size. This flag is appropriate for programs that have small thread stack size

requirements and/or create several thousand threads, with the potential for running

out of virtual memory. Append the letter k or K to indicate kbytes, and m or M for

megabytes. <size> must be > 1000 bytes.

-Xss512k (Java™ 1.3, 1.4, and 5.0 32-bit mode)

Defaults:

-Xss1m (Java™ 1.4 and 5.0 64-bit mode)

NOTE: The default stack size for 1.4 and 5.0 64-bit mode JVM - created threads is

1MB. On PA-RISC 32 and 64-bit systems, the default stack size is 64 KB. Therefore, if

you are using C language main programs that attach with JNI, you will want to adjust

the stack size to avoid overflows.

-Xusealtsigs (replaces -XX:+UseSIGUSR2 beginning with SDK 1.3.1.13, 1.4.1

and 1.4.2)

Instructs the JVM to avoid using SIGUSR1 and SIGUSR2 for internal operations (like

Thread.interrupt() calls). In SDK 1.4.1 and later, by default the JVM uses both

SIGUSR1 and SIGUSR2. In SDK 1.3.1.13 only SIGUSR1 is used. If -Xusealtsigs is

used, then two signals halfway between SIGRTMIN and SIGRTMAX will be chosen

instead.

-Xverbosegc<options>

The -Xverbosegc option prints out detailed information about the spaces within the

Java™ Heap before and after garbage collection.

Beginning with 1.3.1.14 and 1.4.2.05, the process id will be automatically appended to

the verbosegc filename you specify. This helps you to associate a verbosegc output

with the corresponding Java™ process, especially in cases where an application executes

several Java™ processes.

The syntax of the option is:

-Xverbosegc[:help]|[0|1][:file=[stdout|stderr|<filename>]]

• For Java™ 1.2 and 1.3 -Xverbosegc:help detailed explanation

• For Java™ 1.4.0, -Xverbosegc:help detailed explanation

• For Java™ 1.4.1 and 1.4.2, -Xverbosegc:help detailed explanation

• For Java™ 5.0, -Xverbosegc:help detailed explanation

20 HotSpot Technology Tools and Commands

剩余97页未读，继续阅读

mysteryboy2000

粉丝: 6
资源: 5

HP-UX Java性能优化指南（日文高清版）

上海培训_ISMP主机系统__HP-UX性能调优

HP-UX老三篇,学习HP-UX的入门书籍

HP-UX Java应用性能调优：系统监控与解决策略

HP-UX上Java性能调优入门指南：实战步骤

HP-UX Java应用：调优避免过度线程与资源竞争

HP-UX上Java应用性能调优基础

HP-UX中的Java应用性能调优概述.doc

Tomcat优化-Tomcat 的性能调优的原理和方法

HP-UX上BEA Tuxedo性能调优

HP_UX.rar_HP-UX_HP-UX 参考手册_hp ux

最新资源