Ravindra BagaleCourses & study guides

27. Performance Tips

27.2 Performance Analyzer

  1. Optimize › Performance analyzer (in older versions: View › Performance analyzer).
  2. Click Start recording, then Refresh visuals (or interact with slicers).
  3. 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
  1. Expand a visual and click Copy query to analyse the DAX in DAX query view or in the free community tool DAX Studio.
  2. 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

A common Performance Analyzer mistake is 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. Don't worry – after doing it two or three times, it becomes a habit.