Spotlight on Oracle 10.5 - Getting Started Guide

Use this page to predict what resources (CPU, memory, and disk) are required by a hypothetical increase in database throughput and database concurrency.

Specifically, you can use it to perform these tasks:

Predict resource requirements now for a hypothetical database load.
Predict resource requirements for a future date, based on the expected database load at that date.
Predict the maximum resource requirements for a combination of hypothetical and expected loads.

To open this page

Select the Spotlight on Oracle connection in the Spotlight Browser.
Click Predictive Diagnostics | What Database Resources Are Needed?.

Set the criteria

Set the parameters for predicting what resources are needed

Control	Description
Perform an analysis of...	Select Real Data (your database) or Sample Data (to experiment with). Note: Spotlight takes some time (typically about 10 days) to collect enough data to make valid predictions on the future performance of your Oracle instance. In the meantime use the prepared sample data to learn more about Predictive Diagnostics and how it works.
Within the processing period...	Select an activity period to use for your prediction. The more selective this is the better the prediction. Tip: To define new processing periods or redefine an existing processing period see Peak Processing Periods.
For all collected data or For data collected since...	Click all or the date to open Performance Modeling Oracle Job. If you select a start date in Data Analysis Options then this text reads For data collected since.... Note: The start date should be a date for which recorded data exists. For example, you cannot select a date later than today's date. Use this setting to ignore data that occurred before a specific time.
Analyze Disk I/O for.	The Predictive Diagnostics metric for disk utilization can be either disk latency or disk throughput (Disk Latency And Disk Throughput). Select the one that best suits your environment.
Predict forward until...	Select an end date for the prediction.

Set a hypothetical load and view its expected use of database resources

Once you have set the parameters for the analysis, use the hypothetical load prediction to view how your current setup would cope with a change in the amount of data processed by the database (throughput) and the number of users connected to it (concurrency). To do this:

A.	Under Predict resource requirements... select hypothetical database load.
B.	Choose how you want to predict the hypothetical load. Select one of these options and enter the required data for: A percentage of the current values for your choice of Throughput Metrics and Concurrency Metrics, OR Specified values for your choice of throughput and concurrency metrics. (The default value is the current value.)
C.	Wait for Spotlight to model the effect of the hypothetical load on database resources. The result is shown in the bar chart Resource Utilization for Hypothetical Database Load. The bars represent usage for CPU, memory and the chosen disk I/O metric (latency or throughput). The broken red line represents the ceiling for every resource plotted in the chart. You can define your own resource ceilings. Database Resource Ceilings Vertical "error bars" represent the measure of uncertainty in the prediction. Uncertainty In Resource Utilization
D.	Click Show Database Throughput and Concurrency by Time to open a sub-page where you can view the expected database load over time. Use this sub-page to chart the effect of a hypothetical increase in database load when you do not know the size of the increased load. (What would happen, for example, if the database throughput increased by 50%?) Note: The two charts in this sub-page are the same as the equivalent charts in the Why Will Database Resources Reach Their Ceiling? \| Database Throughput And Concurrency page.

Set a future date and view the expected use of database resources at that time

Once you have set the parameters for the analysis, use the Expected database load prediction to view a prediction of how your current setup will cope with the expected database load at a set date in the future. To do this:

A.	Under Predict resource requirements... select Expected database load.
B.	Choose the date for which you want to view the expected database load. How far into the future? The further you look into the future, the less accurate the prediction will be. Its accuracy depends on the time spanned by the existing raw data, NOT on the time-span displayed in the chart.
C.	Wait for Spotlight to model the effect of the expected load. The result is shown in the bar chart Resource Utilization by Time. The bars represent usage for CPU, memory and the chosen disk I/O metric (latency or throughput). The broken red line represents the ceiling for every resource plotted in the chart. You can define your own resource ceilings. Database Resource Ceilings Vertical "error bars" represent the measure of uncertainty in the prediction. Uncertainty In Resource Utilization
D.	Click Show Database Throughput and Concurrency by Time to open a sub-page where you can view the expected database load over time. Use this sub-page to chart the effect of a hypothetical increase in database load when you do not know the size of the increased load. (What would happen, for example, if the database throughput increased by 50%?) Note: The two charts in this sub-page are the same as the equivalent charts in the Why Will Database Resources Reach Their Ceiling? \| Database Throughput And Concurrency page.

Set BOTH a hypothetical load AND a future date...

Under Predict resource requirements... select BOTH hypothetical database load AND Expected database load.

Select one of these options for the hypothetical database load and enter the required data for:

A percentage of the current values for your choice of Throughput Metrics and Concurrency Metrics, OR
Specified values for your choice of throughput and concurrency metrics.

AND choose the date for which you want to view the expected database load.

Click Show Database Throughput and Concurrency by Time to open a sub-page where you can view the expected database load over time.

Note: The two charts in this sub-page are the same as the equivalent charts in the Why Will Database Resources Reach Their Ceiling? | Database Throughput And Concurrency page.

View a summary of each analysis, together with recommendations on what to do next

Predictive Diagnostics generates a separate Resource Utilization summary for each option (hypothetical database load or expected database load, or a combination of both) under Predict resource requirements...

Until you click Show Database Throughput and Concurrency by Time, the page displays only the top summary, whose contents relate to the option under Predict resource requirements... It shows:

The resource utilization predicted for the hypothetical situation. expected date, or both.
The status of each resource type (CPU, memory, or Disk I/O).
What to do next to reduce the impact of a resource limit.

When you click Show Database Throughput and Concurrency by Time, the bottom summary displayed is the same as that shown in the Why Will Database Resources Reach Their Ceiling? | Database Throughput And Concurrency page.

Notes:

Click a Show Details item to see more details on the summary.
Click a link to go to a related Predictive Diagnostics page, or to view additional information.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem