Chapter 8. DB2
143
Asynchronous I/O
In general, DB2 users cannot explicitly choose synchronous or asynchronous I/O. However,
to improve the overall response time of the database system, minimizing synchronous I/O is
preferred and can be achieved through correct database tuning. Consider the following items:
Synchronous read I/O can occur when a DB2 agent needs a page that is not in the buffer
pool to process an SQL statement. In addition, a synchronous write I/O can occur if no
clean pages are available in the buffer pool to make room to bring another page from disk
into that buffer pool. This situation can be minimized by having sufficiently large buffer
pools or setting the buffer pool size to automatic to allow STMM to find its optimal size, in
addition to tuning the page cleaning (by using the
chngpgs_thresh
database parameter).
Not all pages read into buffer pools are done synchronously. Depending on the SQL
statement, DB2 can prefetch pages of data into buffer pools through asynchronous I/O.
When prefetching is enabled, two parallel activities occur during query processing: data
processing and data page I/O. The latter is done through the I/O servers that wait for
prefetch requests from the former. These prefetch requests contain a description of the I/O
that must satisfy the query. The number of I/O servers for a database is specified through
the
num_ioservers
configuration parameter. By default, this parameter is automatically
tuned during database startup.
For more information about how to monitor and tune AIO for DB2, see Best Practices for DB2
on AIX 6.1 for POWER Systems, SG24-7821.
I/O Completion Port (IOCP)
You should configure the AIX I/O completion port for performance purposes, even though it is
not mandatory, as part of the DB2 10.1 installation process. For more information, see
Configuring IOCP (AIX), available at:
http://pic.dhe.ibm.com/infocenter/db2luw/v10r1/index.jsp?topic=/com.ibm.db2.luw.ad
min.perf.doc/doc/t0054518.html
After IOCP is configured on AIX, then DB2, by default, capitalizes on this feature for all
asynchronous I/O requests. With IOCP configured, AIO server processes from the AIX
operating system manage the I/O requests by processing many requests in the most optimal
way for the system.
For more information about this topic, see 8.8, “Related publications” on page 144.
8.6 Capitalizing on performance tooling
Correct performance tooling is crucial for maximizing DB2 performance. Zoning in on
potential performance bottlenecks is impossible without a strong performance tool set, such
as the ones on Power Systems.
8.6.1 High-level investigation
During the general analysis of any performance investigation, the identification of the system
resource bottlenecks is key to determining the root cause of the bottleneck. System resource
bottlenecks can be classified into several categories, such as CPU bound, IO bound, network
bound, or excessive idling, all of which can be identified with AIX system commands.
Содержание Power System POWER7 Series
Страница 2: ......
Страница 36: ...20 POWER7 and POWER7 Optimization and Tuning Guide...
Страница 70: ...54 POWER7 and POWER7 Optimization and Tuning Guide...
Страница 112: ...96 POWER7 and POWER7 Optimization and Tuning Guide...
Страница 140: ...124 POWER7 and POWER7 Optimization and Tuning Guide...
Страница 162: ...146 POWER7 and POWER7 Optimization and Tuning Guide...
Страница 170: ...154 POWER7 and POWER7 Optimization and Tuning Guide...
Страница 222: ...POWER7 and POWER7 Optimization and Tuning Guide POWER7 and POWER7 Optimization and Tuning Guide...
Страница 223: ......