Publishing Reports to the Web - Downloads - Oracle

20.1 Methodology
20
Tuning Oracle Reports
As your reporting requests grow in size and complexity and your user base increases,
you need to consider streamlining your report's performance (or your report’s
execution time) as much as possible. This maximizes its reach and minimizes its
delivery time. Consider the following essentials before you proceed to tune Oracle
Reports:
■ Performance and the trade-offs that occur when improving both perceived and
measurable performance.
■ Costs involved.
■ Computing environment’s complexity.
Investigating some of these areas can result in significant performance improvements.
Some may result in minor performance improvements and others may have no affect
on the actual report performance but can improve the perceived performance.
Perceived performance refers to events that contribute —behind-the-scenes— to the
end-result (measured in terms of the final output). See Fetching Ahead, for an
example of perceived performance.
This chapter provides a number of guidelines and suggestions for good performance
practices in building, implementing, and tuning individual Oracle Reports. The
suggestions given are general in nature and not all suggestions might apply to all
cases. However, implementing some or all of the points in a given application
environment should improve the performance of report execution (real and
perceived).
Note: This chapter does not address Oracle Reports deployment
or scalability issues. Refer to the Oracle Application Server Reports
Services Scalability white paper on OTN,
(http://otn.oracle.com) for more information.
This chapter contains Methodology as the main section.
You must not look at the report in isolation, but in the context of:
■ The application requirements
■ The correctness of the underlying data model
■ The environment where this report will run (for example, client/server, the Web,
or before firewalls)
Tuning Oracle Reports 20-1