Gen2 and notion of overloader/overloaded

[Bamak]

Hi dear PBI friends

Under Gen2, in the event of a lack of available CPU, we can see the notion of overloader / overloaded (sort of wait queue)

Does this only concern rendering & visual navigation ? 

If  the capacity is facing a CPU stress   ?  -> effect -> report DAX queries are overloaded   ?

                                                                                  the report or the whole underlying  dataset is overloaded?

Or also that touch datasets refreshes ?   -> effect -> the entire DS is overloaded in the event of stress   ?

Thank you please for the help and clarification

Best regards

Christophe 

[nickyvv]

Hi @Bamak,

good questions. I'm not sure if you have access to the App itself, I'm assuming you do so here's my 2 cents:

The documentation of the App actually provides a vast amount of clarifications, like:

• an overloaded artifact causes the whole (Premium) capacity to be overloaded, so all datasets/reports on that capacity may be impacted
• Overloaded minutes in the Matrix visual on the Overview page shows the artifacts impacted by an overload. You can also look on the evidence page for more detail.
• On the Evidence page there are also Overloaders/Overloaded artifacts. Sorting by the Overloading score should give you the highest overloaders in that time frame.
  On the graph below (in the top right corner of the page) you can see whether that's for refreshes (background) or rendering/visuals (interactive).
  

Hope this helps.