Oracle EPM 11.1.2.3 性能优化指南

需积分: 10 146 浏览量更新于2024-07-23 1 收藏 1.51MB PDF 举报

"Oracle_EPM_11_1_2_3_Tuning_Guide_v2" Oracle EPM（Enterprise Performance Management）11.1.2.3调优指南提供了针对Oracle融合版EPM系统的性能优化策略。该文档适用于EPM 11.1.2.2和11.1.2.3版本，由Oracle公司于2013年10月发布，旨在帮助用户提升系统的整体效能。在开始系统调优之前，文档强调了免责声明，指出所有调优信息仅供参考，任何修改都应经过测试，并且需要监控和分析其影响。在实施调优设置之前，建议进行端到端的性能测试，以获取默认配置的基准性能数据，然后逐步调整调优设置并收集性能数据，以避免可能对系统性能产生的负面影响。文档的主体内容分为多个部分，以下是一些关键知识点： 1. **性能概述**： - **Oracle EPM系统性能介绍**：这部分介绍EPM系统性能的基本概念，包括系统响应时间、吞吐量和并发用户等关键指标。 - **性能术语**：详细解释了与性能相关的术语，如CPU利用率、内存使用率、I/O延迟等。 - **理解关键性能驱动因素**：讨论了影响EPM系统性能的主要因素，如硬件配置、操作系统设置、数据库性能以及网络环境等。 2. **顶级调优推荐**： - **调优操作系统参数**：这部分指导用户如何调整操作系统级别的设置，如内存分配、进程调度和I/O控制，以优化EPM服务的运行环境。 - **调优Oracle WebLogic Server**：WebLogic作为EPM的一部分，其配置对于整体性能至关重要。这部分涵盖了JVM参数调整、线程池配置、网络连接器优化等方面。 - **数据库调优**：EPM依赖于数据库存储和处理数据，因此数据库的性能优化也是关键。这可能包括索引策略、查询优化、缓存设置等。 - **网络和硬件优化**：涉及网络带宽管理、硬件升级、负载均衡和冗余策略等，确保数据传输的高效性和系统的高可用性。 3. **监控和分析**：这部分介绍了如何使用各种工具和技术来监控系统性能，识别瓶颈，并进行性能分析，以便做出有针对性的调优决策。 4. **案例研究和最佳实践**：可能包含实际应用中的调优案例，分享了成功优化的经验和教训，为用户提供实战参考。 Oracle EPM 11.1.2.3调优指南是优化EPM系统性能的重要参考资料，通过遵循其中的建议和步骤，用户可以有效地提高系统的稳定性和效率。

YIELDLOOPTIME

Controls the number of times to yield the

processor before blocking on a busy lock (only for

libpthreads). The processor is yielded to another

kernel thread, assuming there is another runnable

kernel thread with sufficient priority.

If threads are going to sleep often (lot of idle

time), then the YIELDLOOPTIME might not be

high enough.

Increasing the value from the default value of 0

may benefit you if you do not want the threads to

go to sleep while they are waiting for locks.

- YIELDLOOPTIME=0 -YIELDLOOPTIME=20

SPINLOOPTIME

Controls the number of times the system will

retry a busy lock before yielding to another

process. The default value is 40. This should be

increased to 500 or higher because a busy lock

retry is inexpensive compared to the alternative.

Use the tprof command to determine if the

check_lock routine has high CPU usage. If it does,

you can increase the value even more.

- SPINLOOPTIME=40 -SPINLOOPTIME=500

MALLOCOPTIONS

This environment variable enables the use of

multiple memory heaps. In a highly threaded

environment (e.g. Essbase), many threads can

request memory at the same time. With only one

heap, these requests can serialize and create wait

situations. With this variable, multiple heaps are

generated that are used to serve memory-

allocations requests and reduce memory-

allocation latency

Tip: Malloc multiheap is not enabled by default. It

is enabled and configured by setting the

MALLOCOPTIONS environment variable. To

enable malloc multiheap with the default settings,

set MALLOCOPTIONS=multiheap in Essbase

startup environment file.

Disabled -

MALLOCOPTIONS=multi

heap:16,considersize

For more information about AIX tuning, you should consult your AIX vendor’s

documentation. Note the above TCP/kernel tunable parameters and their

corresponding values are provided as examples and rough guidelines only. You can

adjust these and other parameters based on actual system load, usage patterns such

as the number of concurrent users and sessions and so on.

Important Note to remember for Essbase only: In some cases for AIX 5.3/6.1 the

default Virtual Memory Manager (VMM) settings are not optimal for an Essbase

environment. Common symptoms include high paging, high system CPU time and

slow overall system throughput. Therefore in this scenario, it is recommended to

lower maxperm/maxclient to get good performance.

Important Note to remember for Essbase BSO only: In some cases for AIX

5.3/6.1/7.x the disks are configured in JFS2 for Essbase. AIX classifies memory into

two categories: file cache and working storage. Over time, memory use grows with

both types of memory. AIX will eventually need to free memory and it can do so by

freeing either file cache or working storage. To maximize performance, you would

want AIX to release the type of memory not being used by the application. So for

databases, which use working storage, you would want AIX to release file cache

memory first. To do so in the past, you would put a strict limit on JFS2 file cache

memory using maxclient. It is not unusual to see database servers with file cache

limited to 15% of total memory. However, a strict limit is not always desirable.

The new "lru_file_repage" option solves this problem. By setting "lru_file_repage=0",

AIX only frees file cache memory. This guarantees working storage stays in

memory, and allows file cache to grow.

So in the past you might have set maxclient at 20% for database servers. Today you

could set maxclient at 90% and "lru_file_repage=0". The exact setting will vary

based on your application and amount of memory. Contact IBM Support if you need

help determining the optimum setting.

Full example on AIX for Essbase:

vmo -p -o maxperm%=90 -o maxclient%=90 -o minperm%=3 -o lru_file_repage=0

Useful documentations:

• http://www-01.ibm.com/support/docview.wss?uid=swg21328602

• https://www.ibm.com/developerworks/community/blogs/aixpert/entry/ne

w_aix_memory_tuning_option?lang=en

2.1.5 Oracle Sun Solaris Tuning Parameters

This topic describes how to tune the Solaris operating system to optimize the

performance of your Oracle® EPM System. Note: Solaris default network tuning

parameters should be sufficient in most cases. For heavy, network centric

workloads, it’s always best practice to increase the size of key TCP-related

parameters to improve system performance and reduce dropped connections.

Parameter Default Value Suggested Value

File descriptors (nofiles)

Important Note: On any box that hosts an Oracle

HTTP Server / WebLogic Server / Essbase server it is

recommended to increase nofiles (descriptors) to

optimal value. On Solaris this means setting the

“rlim_fd_cur” in the /etc/system file and rebooting the

box.

Please make sure to check your operating system

documentation and release notes; there are some

negative performance implications on some older

versions of Solaris if you set these numbers too high.

Tip: The syntax for adjusting this parameter in the

/etc/system file is shown below:

set rlim_fd_cur=16384

256

16384

tcp_time_wait_interval

It is recommended to reduce this setting to 60,000

milliseconds, or 1 minute; this is the default value starting

in Solaris 9/10. By reducing the value of this entry,

TCP/IP can release closed connections faster, providing

more resources for new connections.

Tip: The command

“

netstat -a | grep TIME_WAIT | wc -l”

will count all of the TCP connections that are in the

TIME_WAIT state. As this number approaches the

maximum number of file descriptors per process, your

application’s throughput will suffer dramatic

degradations because new connection requests may

have to wait for a free space in the application’s file

descriptor table. Tip: Set using command:

ndd -set /dev/tcp tcp_time_wait_interval 30000

60000

30000

tcp_xmit_hiwat (Solaris 9/10) / send_buf (Solaris 11)

The tcp_xmit_hiwat (tcp_send_buf) and

tcp_recv_hiwat (tcp_recv_buf) parameters control the

default size of the send window and receive window

for each TCP connection. On very fast networks, you

should make sure that the values are set to at least 32K.

By default, Solaris 9 changes the default settings for

49152

This parameter is calculated

based on the network

bandwidth and latency. You

could follow this rule to

calculate:

<numbers of bits per second> *

<roundtrip latency> * 8

[bits/byte]

both parameters to 48K.

tcp_recv_hiwat (Solaris 9/10) / recv_buf (Solaris 11)

The tcp_xmit_hiwat (tcp_send_buf) and

tcp_recv_hiwat (tcp_recv_buf) parameters control the

default size of the send window and receive window

for each TCP connection, respectively. On very fast

networks, you should make sure that the values are set

to at least 32K. By default, Solaris 9 changes the default

settings for both parameters to 48K.

49152

(in Solaris

9/10)

128000

(in

Solaris 11)

This parameter is calculated

based on the network

bandwidth and latency. You

could follow this rule to

calculate:

<numbers of bits per second> *

<roundtrip latency> * 8

[bits/byte]

tcp_conn_hash_size (Solaris 9) / ipcl_conn_hash_size

(Solaris 10/11)

This parameter controls the size of a hash table that

helps quickly locate the TCP socket’s data structure in

the kernel. If the size is too small, it will result in long

hash chains in each bucket that force the operating

system into a linear search for the socket entry of

interest, and performance will suffer accordingly.

512

(in Solaris 9)

(in Solaris

10/11)

1024 (in Solaris 9)

In Solaris 10, the default

value of 0 means that the

system automatically

sizes an appropriate

value for this parameter

at boot time, depending

on the available

memory.

Connection backlog

This parameter controls the maximum allowable

number of completed connections waiting to return

from an accept call (that have completed the three-way

TCP connection handshake). You should increase this

parameter only if you notice that your system is

dropping connections.

Increase these values if you do see non-zero values for

tcpListenDrop in the output for the following

command:

netstat –s | fgrep –i listendrop

Increase the values in steps of 256 starting from the

default value

Tip: Set using commands:

ndd -set /dev/tcp tcp_conn_req_max_q 1024

ndd -set /dev/tcp tcp_conn_req_max_q0 4096

128 (max_q)

1024 (max_q0)

1024 (max_q)

4096 (max_q0)

Important Note: It is important to keep systems up to date with Solaris patches

because the patches provide fixes for security vulnerabilities, performance, and

other improvements of the OS. Certain patches specifically target the Java platform, which

benefits WebLogic Server in regards to performance and functionalities.

2.2 Tune Oracle WebLogic Server (WLS) parameters

This topic describes how to tune the WebLogic Server to optimize the performance

of your Oracle® EPM System.

2.2.1 Tuning JDBC Data Sources

You can improve EPM system performance and stability by properly configuring

the attributes in JDBC data sources in your EPMSystem domain.

2.2.1.1 Increase the Number of Connection Pool

If EPM data sources are running out of connections to the relational database then

you need to set the maximum number of connections to high value for the following

EPM data sources:

Important Note: Reason why the default value initial and maximum capacity size

are set to lower value because it is important to protect database resources. So make

sure you have enough resources on the database server (available memory is a constraint). If

you increase initial / maximum capacity to very high value, you may exceed the limit of

PROCESSES / OPEN_CURSORS on Oracle database server.

EPM Data Source Name Default Value Suggested Value

EPMSystemRegistry

Initial Capacity: 1

Maximum Capacity: 150

Initial Capacity: 10*

Maximum Capacity: 150

*Note: Each managed server target to

EPMSystemRegistry data source creates

1 pool on start-up. Ensure you have

enough Oracle processes; refer to Oracle

Database Tuning section of this guide.

raframework_datasource Initial Capacity: 1

Maximum Capacity: 15

Initial Capacity: 1

Maximum Capacity: 150

planning_datasource Initial Capacity: 1

Maximum Capacity: 15

Initial Capacity: 1

Maximum Capacity: 150

financialclose_datasource (FCM) Initial Capacity: 1

Maximum Capacity: 30

Initial Capacity: 1

Maximum Capacity: 150

eas_datasource (Essbase Admin

Services)

Initial Capacity: 1

Maximum Capacity: 15

Initial Capacity: 1

Maximum Capacity: 30

calc_datasource (CalcMgr) Initial Capacity: 1

Maximum Capacity: 15

Initial Capacity: 1

Maximum Capacity: 30

profitability_datasource (Profitability) Initial Capacity: 1

Maximum Capacity: 15

Initial Capacity: 1

Maximum Capacity: 30

hps_datasource (HpsAlerter,

HpsWebReports)

Initial Capacity: 1

Maximum Capacity: 15

Initial Capacity: 1

Maximum Capacity: 30

discman_datasource

(DisclosureManagement)

Initial Capacity: 1

Maximum Capacity: 15

Initial Capacity: 1

Maximum Capacity: 30

aif_datasource (ErpIntegrator) Initial Capacity: 1

Maximum Capacity: 120

Initial Capacity: 1

Maximum Capacity: 200

Important Note: You need to determine the optimal value for the Initial and Maximum

Capacity as part of your pre-production performance testing. Once optimal values are

剩余109页未读，继续阅读

lyhln1314

粉丝: 0
资源: 2

Oracle EPM 11.1.2.3 性能优化指南

epm分区工具

EPM 无损分区软件

SAP BPC EPM中文手册，中文版手册

EPM240.rar_ EPM240 _CPLD 开发板_EPM2_epm24_epm240 vhdl

EPM240-570T100-SCH.rar_EPM240 原理图_epm240_epm240 sch_epm570t100开

lcd.rar_LCD DE CP_epm240_epm240 T_epm3064驱动lcd_vhdl lcd

armledctl.rar_ vhdl epm240_armledctl_epm240_epm240 sram_verilog

EPM240原理图.rar_EASYCPLD_EPM240 BOARD_cpld epm240_epm240_原理图

EPM570_1270T.rar_EPM570_EPM570T100_max_max ii_含有epm1270的库

PWM.rar_EPM1270_EPM1270 PWM_fpga PWM _vhdl epm1270_基于FPGA+PWM

最新资源