Note: Available for Oracle 10.2 and later.
Use this page to predict what database load can be supported by a hypothetical mix of CPU, memory, and disk resources.
To open this page
Click Predictive Diagnostics | What Database Load Can Be Supported?.
Choose these parameters for your analysis.
Note: The parameter settings initially are the same as those in the What Database Resources Are Needed? page.
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. | ||||||||||
Since... |
Choose a date to use as the start date for the period to be analyzed. Choose a date for which recorded data exists; for example, you cannot choose a date later than today's date. | ||||||||||
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. | ||||||||||
Predict forward until... |
Select an end date for the prediction. | ||||||||||
Using...for database throughput |
Choose a metric to represent the total amount of work performed. Throughput Metrics
| ||||||||||
Using...for database concurrency |
Choose a metric to represent database concurrency.Concurrency Metrics
|
Predict the database load that can be supported by the entered combination of CPU, memory, and disk resources.
Note: Because the values are entered as a percentage of the resources now available, the prediction makes no judgments on how database resources may be implemented. (For example, a prediction for 200% of the current CPU resources does not depend on whether the increase is implemented as a more powerful single CPU, multiple additional CPUs, or a combination of both.)
Resource |
Description |
---|---|
Current CPU |
Enter a hypothetical value for the CPU resources available to the database. |
Current Memory |
Enter a hypothetical value for the memory resources available to the database. |
Current Disk |
Enter a hypothetical value for the disk resources (Disk Latency And Disk Throughput) that can be made available to the database. Choose the metric that is more appropriate to the database environment. |
The charts display the prediction for database load resulting from the given combination of CPU, memory, and disk resources.
Analysis |
Description |
---|---|
Resource Utilization by Time |
How database resources will be consumed over time, given the hypothetical values for CPU, memory, and disk resources. |
Resource Utilization by Database Throughput |
How resource utilization varies with the metric (logical reads/s, rows processed/s, SQL executions/s, or transactions/s) chosen to represent database throughput. |
Resource Utilization by Database Concurrency |
How resource utilization varies with the metric (connected sessions, active sessions, or a customized metric) chosen to represent database concurrency. |
Notes:
The pane at the right provides a summary of the analysis used to draw the charts on the left, and indicates:
Notes:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center