This is from Oracle guru Tanel Poder site:"as we should be really measuring end user response time breakdown at session level and asking questions like what throughput/response time do you normally get."
So, this is the key - query is either running or waiting. So, we need to have an established mechanism for detecting query waits. Part of that process is analyzing query plan, but waits are crucial. Waits can also give us additional info that something wrong is with execution plan, that some index is missing, that there high contention on some database resources.
So, focus on waits :-) This is what I am doing after 10 (exactly 13) years of database development and DBA activities. I needed lots of time to get to that simple conclusion - and that is - query is running or waiting. If it is waiting find out why and what it is waiting for. Simple as that :-)
So, this is the key - query is either running or waiting. So, we need to have an established mechanism for detecting query waits. Part of that process is analyzing query plan, but waits are crucial. Waits can also give us additional info that something wrong is with execution plan, that some index is missing, that there high contention on some database resources.
So, focus on waits :-) This is what I am doing after 10 (exactly 13) years of database development and DBA activities. I needed lots of time to get to that simple conclusion - and that is - query is running or waiting. If it is waiting find out why and what it is waiting for. Simple as that :-)
