How to Reproduce First-Time Loading Slowness in Power BI (Live Connection)?

Hi  

1. Dataset Eviction / Idle Timeout

Power BI datasets in the service go idle after 60 minutes (sometimes as low as 20–30 min depending on resource load). When a dataset goes idle:

• The in-memory model is paged out to conserve resources.

• The next query wakes it up, causing a cold start.

• Cold start includes rehydrating metadata, restoring memory context, and priming caches.

  2. Query Plan Recompilation

  On the first access, some DAX queries might:

  Trigger query plan caching
  
  

  Force VertiPaq engine to reload dictionaries or precompute expressions.

  How to Reproduce Cold Start Slowness Faster

  🔁 Option 1: Use REST API to Refresh Dataset Memory

  Use the Power BI Admin REST API to:

  • Clear memory cache or simulate inactivity.
    Unfortunately, Power BI doesn't offer a direct unload dataset API, but...

    🧊 Option 2: Use Multiple Tenants or Incognito

    Try accessing the report from:

    • Incognito mode or a browser profile not used for 30+ min.

    • Different user accounts or new Power BI Desktop sessions.

      🧨 Option 3: Restart or Rotate Workspace Capacity

      If you're on Premium Capacity, go to the Admin Portal → Capacity Settings:

      • Restart the capacity to flush everything.

      • Or, assign the dataset to a new capacity.

        🔁 Option 4: Use a Proxy or VPN

        Session affinity and caching might be tied to location/IP. Try:

        • Switching VPN endpoints.

          Using a proxy to simulate a "new user" behavior.
          
          

          Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!

Zhinee