[Documentation] Document guidelines for detecting cached sql calls
From the parent epic - Provide metrics that would help us to detect the potential N+1 CACHED
SQL calls
We have comments in the epic with metrics we are using to detect the cached SQL calls - &3873 (comment 378279982). This should be documented in our developer docs and/or handbook.
- How to detect
- What to look for
- Consider repeatable and consistent data vs. spikes
- How to measure impact of change
This documentation should be provided for other development teams to enable them to be able to detect similar inefficiencies and fix themselves.
Edited by Nikola Milojevic