Oracle OBIEE 12c 调优指南：最佳实践

需积分: 10 35 浏览量更新于2024-07-17 收藏 2.06MB PDF 举报

"Oracle_OBIEE_12c__Tuning_Guide_-_v3.pdf" Oracle OBIEE 12c 调优指南是一个针对企业级性能优化的实践手册，强调了调优是一个迭代过程，需要通过测试和监控来分析其影响。在实施任何调优设置之前，建议进行端到端的性能测试，获取默认配置的基线性能数据，逐步调整调优设置，并收集性能数据，以避免可能对系统性能产生的负面影响。该文档的目录结构包含以下几个主要部分： 1. **介绍**：这部分可能涵盖了Oracle Business Intelligence Enterprise Edition (OBIEE) 12c性能的基本概念，解释了为什么性能优化是必要的，以及如何理解和评估OBIEE的性能。 2. **性能概述**：可能深入探讨了OBIEE性能的关键驱动因素，包括但不限于数据处理、查询优化、硬件配置和网络延迟等。 3. **顶级调优建议**：这部分将提供针对OBIEE 12c的一系列最佳调优实践。可能包括数据库优化、操作系统参数调整、硬件配置建议等。 - **调优操作系统参数**：文档分别列出了针对不同操作系统的调优参数，如： - **Linux调优参数**：可能涉及内核参数、内存管理、I/O调度器等方面的优化。 - **Windows Server 2012调优参数**：可能涵盖进程调度、内存分配、磁盘I/O等方面的调整建议。 - **AIX调优参数**：IBM AIX系统特有的调优建议，可能包括系统资源管理、并行执行和服务质量等方面。 - **Oracle Sun Solaris调优参数**：可能包括项目调度、虚拟内存管理和网络优化等。 4. 后续章节可能还涉及到其他的硬件和软件调优，例如数据库服务器配置、Web服务器配置、缓存策略、报告和分析性能优化，以及监控和诊断工具的使用等。这份指南提供了全面的OBIEE 12c基础设施调优最佳实践，旨在帮助管理员和IT专业人员提升系统的响应速度、并发用户支持能力和整体性能。通过遵循这些指南，可以确保OBIEE系统在复杂的企业环境中高效运行，满足业务需求。

2.1.4 Oracle® Sun Solaris Tuning Parameters

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

performance of your Oracle® Business Intelligence Enterprise Edition. 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.

Sun Solaris Parameter

Default Value

Suggested Value

File descriptors (nofiles)

Important Note: On any box that hosts an Oracle®

HTTP Server / WebLogic Server / OBIEE

(Presentation/BI) 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=65535

256

65535

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 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

The tcp_xmit_hiwat and tcp_recv_hiwat parameters

control the default size of the send window and receive

window for each TCP connection. On very fast

49152

This parameter is calculated

based on the network

bandwidth and latency. You

could follow this rule to

calculate:

networks, you should make sure that the values are set

to at least 32K.

<numbers of bits per

second> * <roundtrip

latency> * 8 [bits/byte]

tcp_recv_hiwat

The tcp_xmit_hiwat and tcp_recv_hiwat 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.

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]

ipcl_conn_hash_size

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.

(in Solaris 10)

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® Business Intelligence Enterprise Edition.

2.2.1 Tuning JDBC Data Sources

You can improve Oracle Business Intelligence Enterprise Edition performance and

stability by properly configuring the attributes in JDBC data sources in your

bifoundation_domain domain.

2.2.1.1 Increase the Number of Connection Pool

If JDBC (BI) data sources are running out of connections to the RCU relational

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

the following Business Intelligence Enterprise Edition data sources:

Important Note: The reason why the default value maximum capacity size is set to

lower value is 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.

Data Source Name

Default Value

Suggested Value

biplatform_datasource

Initial Capacity: 0

Maximum Capacity: 200

Initial Capacity: 0

Maximum Capacity: 500

LocalSvcTblDataSource

Initial Capacity: 0

Maximum Capacity: 200

Initial Capacity: 0

Maximum Capacity: 500

mds-owsm

Initial Capacity: 0

Maximum Capacity: 15

Initial Capacity: 0

Maximum Capacity: 500

opss-audit-DBDS

Initial Capacity: 0

Maximum Capacity: 15

Initial Capacity: 0

Maximum Capacity: 500

opss-audit-viewDS

Initial Capacity: 0

Maximum Capacity: 15

Initial Capacity: 0

Maximum Capacity: 500

opss-data-source

Initial Capacity: 0

Maximum Capacity: 15

Initial Capacity: 0

Maximum Capacity: 500

wlsservices_datasource

Initial Capacity: 0

Maximum Capacity: 200

Initial Capacity: 0

Maximum Capacity: 500

Important Note: You need to determine the optimal value for the Maximum Capacity as

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

then set the value of Initial Capacity equal to the value for Maximum Capacity in

order to boost performance of JDBC in WebLogic Server web applications.

Tip: Here is the example on how to size open cursors value on Oracle® database, if

you have a data source with 150 connections deployed on 1 server and if you use

剩余59页未读，继续阅读

我不是加肥猫

粉丝: 0

Oracle OBIEE 12c 调优指南：最佳实践

Oracle OBIEE调优实战指南：优化参数与监控策略

利用Docker部署Oracle OBIEE环境指南

Oracle OBIEE 11.1.6.2 BP1 升级详细步骤

Oracle_OBIEE_Tuning_Guide

__OBIEE学习总结之入门

GA_OBIEE:识别OBIEE中类型页面并将其发送到Google Analytics（分析）JavaScript代码

Oracle_BIEE_11gR1安装指南.pdf

OBIEE学习总结之入门(PDF)-study.pdf

oracle oam-biee.pdf

【原创】ETL_ORACLE BI平台-BIEE 心得.pdf

最新资源