Given a report where a visual's DAX query takes 27 ms, visuals total 39 ms, and other 1047 ms, what change yields the greatest rendering improvement?

• A. Enable automatic page refresh
• B. Optimize the DAX query of Orders By Date by using DAX Studio
• C. Change the visual type of Orders By Date
• D. Reduce the number of visuals in Report1

Answer: (D)

The key idea is that rendering performance on a report page is often dominated by overhead that isn’t tied to a single visual’s data query. In this scenario, the visual’s DAX time is small (27 ms) and the total for all visuals’ DAX work is also modest (39 ms), but there’s a large chunk labeled “other” (1047 ms). That “other” time typically covers layout, rendering, and coordination work for all visuals on the page. By reducing the number of visuals, you cut down the amount of work the engine must do across the whole page, which directly lowers this dominant overhead and yields the greatest overall rendering improvement.

Trying to optimize the DAX of one visual wouldn’t address the large, page-wide rendering overhead. Changing the visual type or enabling features like automatic page refresh could alter rendering costs but wouldn’t reduce the dominant “other” overhead as effectively as simply reducing the number of visuals on Report1.