27.2 Performance Analyzer
- Optimize › Performance analyzer (in older versions: View › Performance analyzer).
- Click Start recording, then Refresh visuals (or interact with slicers).
- Each visual is listed with its duration in milliseconds, split into:
| Part | Meaning |
|---|---|
| DAX query | Time for the engine to run the query – high values point to the model or DAX |
| Visual display | Time to draw the visual – high for visuals with many data points or custom visuals |
| Other | Waiting time (e.g. for other visuals) and preparation work |
| Direct query | (DirectQuery only) Time spent waiting for the source database |
- Expand a visual and click Copy query to analyse the DAX in DAX query view or in the free community tool DAX Studio.
- Export saves the results as a JSON file.
Test fairly
Mitrano, test from a blank page first (so caches are not already warm), then switch to the page you want to measure. Compare before/after timings for each change you make.
Performance Analyzer ha doctor sarkha aahe – aadhi nidan, mag ilaj.
Ravindra Bagale's Tip
Performance Analyzer madhli ek common chuk mhanje recording once with a warm cache and trusting the numbers. Click Refresh visuals while recording, test a few times, and look at DAX query vs Visual display vs Other to know whether the problem is the model, the visual or too many visuals. Ghabru naka, don-teen vela kela ki savay hote.