What is the right time to stop tuning an Oracle database?

Performance tuning is an activity driven by business needs and constrained by resources. The process should continue as long as it provides value and meets defined performance objectives within the allocated budget and timeframe. Once the allocated resources (such as budget or time) are exhausted, or if the cost of further tuning outweighs the performance benefits, the tuning effort should cease. The other options represent technical metrics which are means to an end, not the end goal itself.

B. Eliminating all concurrency waits is often impractical or impossible; the goal is to reduce problematic waits, not all waits.
C. High cache hit ratios are indicators, not guarantees of good performance. A system can have high ratios and still perform poorly due to inefficient SQL.
D. The acceptable percentage of I/O as part of DB time is highly dependent on the workload (e.g., OLTP vs. Data Warehouse) and is not a universal stopping point.

1. Oracle Database Performance Tuning Guide, 19c. Chapter 2, "Designing and Developing for Performance". Section 2.1, "Understanding Performance Management Methodology". The methodology implies tuning is goal-oriented and iterative, not an endless pursuit of ideal metrics.

2. Oracle Database Concepts, 19c. Chapter 1, "Introduction to Oracle Database". Section "Performance Tuning". Performance tuning is described as a task to meet user expectations, which are tied to business goals and resource constraints.