Solution to I/O Landscape of an Application

The buffer gets far right show us the strength of the activity on the corresponding segments.
The list is sorted by Buffergets, which means the segments with the highest activity are on top.
We can actually be pretty sure that theses segments are also the most central and most important of the whole application since they are showing the highest activity.  (If a database corresponds to an application.)
This should be evident: the numbers  in  the report are important.
Normally we would expect that the physical reads behave proportional to the buffer gets. According to the rule of thumb that maximal  10% of buffer gets should be converted into  physical reads. In reality, there is very often a concentration of physical reads on a few segments .
These segments, which have a disproportionate number of physical reads exhibit a bottleneck in physical design. Potential reasons are amongst others missing index or non-clustered data.
A exhaustive research of  all execution plans which reference the bottleneck segments did  reveal the root causes.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s