I really shared the script, which I'm always using in my consulting activities here in Brazil, at no time I thought of writing an article that can illustrate or guide how we can reach this values, maybe do it, even if you want to access my humble blog: pedrogalvaojunior.wordpress.com, may have a dimension of what I do and a little of what I aim to do.
There are several possibilities that can cause the presentation of these values, this will depend very much on what is being executed or even processed by the instance, server or hardware that we are analyzing.
When this script is run in an environment is the values â€‹â€‹presented are close to what I highlighted, we then have to start analyzing their possible causes, by default when faced with a supposedly slow reading process, the main causes can be:
- Hard Disk presenting performance problems in the search of data;
- Fragmentation of data in our tables and indexes;
- Lack of indexes in our tables;
- Use of columns in the where clause that do not satisfy the condition to obtain the data in a better time; and
- As well as the query being executed may be one of the causes.
At this point, you see these items as possible causes of slow reading of data that is on disk.
But reinforcing again that this script is meant to alert the values â€‹â€‹that are being presented at the time of its execution, the causes or reasons will vary from scenario to scenario.