When do you need performance tuning
Sometimes a system performs badly. Or just not as well as you had hoped or expected and the reason why is not immediately obvious to those working with it. We specialize in Oracle Database performance and the many influencers around it that underlie poor performance.
Besides solving current performance problems, we also recommend proactive tuning, which has the following advantages:
- Optimal sizing when buying new hardware.
- A comprehensive insight in DB activity.
- The elimination of unnecessary resources usage.
- An optimization of systems in order to reduce or stabilize the license cost.
Our tuning expertise
Our areas of tuning expertise are:
- DB activity:
- Wait events.
- OS activity:
First we look at overall DB performance, though individual queries and action can be evaluated as a second step as well.
How we do it
We take the following steps to come to our findings and recommendations concerning your performance issues:
Phase 1: Scope & Objectives.
Define the DBs and systems where the problem occurs.
Describe the current architecture (clustering, storage configuration, application servers,…).
Define the purpose of the analysis (HW renewal, issues, consolidation, license cost, …).
Phase 2: Configure the tools.
Apart from using the existing Oracle tools such as AWR, we also have our own monitoring and reporting tools, designed specifically for reading the DB environment in detail and report comprehensively on these measurements:
Plato: gives an overview of the actual structure and settings of the DB.
Pandora: collects and visualizes key performance statistics over time.
Phase 3: Sampling period (minimum one week is recommended).
Phase 4: Analysis.
Creation of the report of findings:
Deep insight in actual DB performance.
Overview of highest resource usage.
Recommendations & quick wins:
Interesting areas for tuning.
Architecture, DB versions, …
DB settings and features.
Phase 5: Presentation & Discussion.
Phase 6: Recurring evaluation (optional).