WebSphere Portal V6.0性能调优指南

WebSphere

Portal

需积分: 7 73 浏览量更新于2024-07-31 收藏 815KB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

"WebSphere Portal V6 调优技术文档，主要涵盖了环境性能调优、应用服务器调优、数据库源调优、集群配置、数据库服务器调优以及操作系统层面的调优等内容。" WebSphere Portal V6 调优指南是针对IBM的WebSphere Portal 6.0版本的一份详尽的性能优化手册。调优是提升系统性能的关键步骤，尤其对于企业级应用如WebSphere Portal，确保其高效稳定运行至关重要。 1. **理解环境**： - 在开始调优前，了解环境的架构和组件是基础。这包括了解应用服务器、数据库、目录服务和网络的配置。 2. **应用服务器调优**： - 优化Java虚拟机（JVM）的堆内存设置，避免因内存限制导致的性能瓶颈。 - 应用服务器克隆是扩展性的重要部分，调优时要考虑复制过程中的性能影响。 3. **数据库源调优**： - 对于DB2数据库，调整数据源参数，如连接池大小，以提高数据访问效率。 - 对于Oracle数据库，也需要类似的参数调优，并规划适合企业规模的企业版数据库配置。 4. **数据库服务器调优**： - DB2数据库服务器的参数调优涉及IBM DB2 Enterprise Edition，包括推荐的数据库维护策略。 - Oracle数据库服务器的调优则包括规划Oracle Enterprise Edition，以及相应的参数调整和维护建议。 5. **目录服务器调优**： - 目录服务作为WebSphere Portal的重要组成部分，其性能优化可以提升用户认证和授权的效率。 6. **Web服务器调优**： - 文件描述符限制：调整系统对打开文件的数量限制，以适应高并发场景。 - 操作系统层面的网络调优，包括对Solaris、AIX、Windows 2003及Linux等不同平台的网络参数优化。这份文档详细列出了各个层面的调优步骤和建议，为管理员提供了全面的指导，以确保WebSphere Portal在复杂的企业环境中能够达到最佳性能。通过这些调优策略，可以减少延迟，提高响应速度，同时增强系统的稳定性和可扩展性。

资源详情

资源推荐

WEBSPHERE PORTAL V6.0 TUNING GUIDE

ManagementÆProcess Definition Æ Java Virtual

Machine

Æ Generic JVM Arguments

- {add} -XX:SurvivorRatio=16

ADDITIONAL NOTES: JVM MAXIMUM HEAP SIZE LIMITS

When setting the heap size for an application server, keep the following in mind:

 Make sure that the system has enough physical memory for all of the processes to

fit into physical memory, plus enough for the operating system. When more memory

is allocated than the physical memory in the system, paging will occur, and this can

result in very poor performance.

 While we set the minimum and maximum heap sizes to the same values, this may

not be the best choice for production systems which are running on IBM JDKs. In

our measurement runs, the system is under load for a relatively short time (around 3

hours), and it is running with portlets which do not have large memory requirements.

When using portlets which have larger memory requirements, or for continuous

operation, it may be possible to reduce heap fragmentation by setting the initial heap

size to 320 megabytes.

 After doing any tuning of heap sizes, monitor the system to make sure that paging is

not occurring. As mentioned above, paging can cause poor performance.

 32-bit operating systems have an address space limit of 4GBytes, regardless of the

amount of physical memory in the system. This limits the maximum size of each

individual process in the system. In addition, some operating systems restrict the

size of processes to be even less than this limit. Many versions of Windows limit

processes to 2GBytes in size; you can find more information at

http://support.microsoft.com/default.

aspx?scid=kb;en-us;555223.

 The address space limit further restricts the size of the JVM process. If the process

grows larger than the limit imposed by the operating system, it may terminate

unexpectedly.

 Linux on System z is a 31-bit environment, which limits each user process to

1Gbyte. To fit within this size limit, we used a heap size of 768Mbytes in this

environment.

Due to the demands on native memory by WebSphere Portal V6.0 and its underlying

components, we chose a maximum heap size of 1280MB in our Windows environments.

This is smaller than previous releases of Portal. There is a balance between JVM heap and

native memory, all of which must fit within the 2GB restriction in 32-bit Windows. 1280MB

WEBSPHERE PORTAL V6.0 TUNING GUIDE

was the largest value we could use to successfully measure all of our Windows

configurations and workloads. If your application has additional native memory

requirements then you may need to choose a smaller maximum heap size. For more

information, see the WebSphere Application Server information center.

DATASOURCE TUNING FOR DB2

As is described in the WebSphere Portal information center, multiple databases are used

with WebSphere Portal V6.0. We used seven separate databases, each representing a

separate database domain and having their own datasources. These are:

Table 1 DB2 Database Domains

Database Database name Datasource name

Release

release reldbDS

Community

community commdbDS

Customization

custom cusdbDS

Feedback

fdbkdb fdbkdbDS

Likeminds

lmdb lmdbDS

JCR

jcrdb jcrdbDS

Member Manager

wmmdb wmmdbDS

All datasources are configured in a similar manner. Log on to the WebSphere Application

Server administrative console. For the prepared statement cache size, the path is

Resources → JDBC Providers → provider name → Data Sources → datasource name.

The provider name and datasource name are based on the names selected for that

database during the database transfer step. Look for the parameter Statement cache size.

For the connection pool settings, the path in the WebSphere Application Server

administrative console is Resources → JDBC Providers → provider name → Data Sources

→ datasource name → Connection Pools. The settings are Minimum connections and

Maximum connections.

The default settings were used for the prepared statement cache size, and connection pool

minimum and maximum sizes. However for the AIX Power 4 measurements the release,

customization and community databases had a prepared statement cache size of 100. Be

aware that specifying a larger statement cache size can lead to OutOfMemory error's in

situations where your application memory is already being highly utilized by your workload.

Also, in some workloads, increasing the prepared cache statement size will be of no

benefit. For instance, on WCM workloads, due to the dynamic nature of the SQL

statements generated against the JCR database the cache size would have to be very

large to cover all of the different permutations and the hit rate would be very low. In such

cases, it is better to decrease the size of the cache to free up memory resources. Finally,

be aware that the prepared statement cache size setting is the maximum allowed cache

entries per database connection so increasing the cache size on a datasource that has a

large number of connections can quickly amplify the heap utilization for these cache

WEBSPHERE PORTAL V6.0 TUNING GUIDE

objects. Any changes should be considered for each individual datasource independently

instead of across all datasources globally. Before increasing a datasource's prepared

statement cache size you should monitor your memory usage under a heavy workload to

determine if there are enough memory resources available to handle an additional

increase.

DATASOURCE TUNING FOR ORACLE

In our Solaris measurements, a single shared database with separate database domains

owned by different Oracle users are used with WebSphere Portal V6.0 running against an

Oracle database. We used seven separate Oracle users, each with their own datasources.

These are:

Table 2 Oracle Database Domains

Database Domain Database User Datasource name

Release

release reldbDS

Community

community commdbDS

Customization

custom cusdbDS

Feedback

fdbkdb fdbkdbDS

Likeminds

lmdb lmdbDS

JCR

jcrdb jcrdbDS

Member Manager

wmmdb wmmdbDS

As described in previous ‘DataSource Tuning for DB2’ section, all datasources and

connection pool settings are configured in a similar manner.

The datasources for the release, customization and community databases had a prepared

statement cache size of 100. The other parameters for these datasources were left at their

default values, and all other datasources used the default values for all settings.

The datasources for the release, customization and community databases had a prepared

statement cache size of 100. Be aware that specifying a larger statement cache size can

lead to OutOfMemory error's in situations where your application memory is already being

highly utilized by your workload. Also, in some workloads, increasing the prepared cache

statement size will be of no benefit. For instance, on WCM workloads, due to the dynamic

nature of the SQL statements generated against the JCR database the cache size would

have to be very large to cover all of the different permutations and the hit rate would be very

low. In such cases, it is better to decrease the size of the cache to free up memory

resources. Finally, the prepared statement cache size setting is the maximum allowed

剩余58页未读，继续阅读

pushicd2011

粉丝: 0
资源: 5

WebSphere Portal V6.0性能调优指南

IBM Portal 调优

Ibm websphere Portal 6.1调优手册

websphere教程

websphere面试题

portal服务器搭建

websphere 示例是什么

websphere mq6 csdn

websphere 部署微服务

websphere工作原理？

websphere中概要的概念

怎么下载安装websphere

ibm websphere mq基础教程

eclipse如何配置websphere 8.5

WEBSphere是Web服务器？

IBM websphere mq 使用

vue项目部署到websphere

websphere9避坑

zabbix 监控IBM websphere

websphere 8.5 安装包 下载

websphere linux

最新资源

websphere 8.5 安装包下载