Forum Discussion
PublishModel fails with ImageLoad on High CPU consumption
Hi,
thanks everyone.
In the moment I go this way with restarting of failed reports at the end of the batch.
I dont know if deeper debugging and configuration of analysis services would really help, and is worth the effort.
I found also this article:
Solved: Re: Power BI Report Server Scheduled Refresh Bottl... - Microsoft Fabric Community
and
Analysis Services thread pool properties | Microsoft Learn
where I can play around with Affinitygroups and thread definitions. But how to find out which ThreadPool is the problem?
Maybe someone got already that deep in configuration of analysis service, and can give a hint how to proceed and if it makes sense here to investigate deeper.
Maybe the only chance is to throttle by maxQueueThreads, but I would like to have the optimal throughput of refreshing reports after the daily load of the DWH is done. And hard throtteling on the number of refreshes.. dont know.. Sounds like a workaround as well.
regards,
Stefan
Advocate IIThis looks like resource contention during concurrent refreshes. I'd try staggering the 4 refresh jobs first and monitor CPU, memory, and disk usage during that window. The timeout and "connection closed by remote host" errors often appear when the Analysis Services engine is under heavy load and becomes unresponsive. Dataset size, available RAM, and your PBIRS version would help identify the root cause.
Hi,
thanks everyone.
In the moment I go this way with restarting of failed reports at the end of the batch.
I dont know if deeper debugging and configuration of analysis services would really help, and is worth the effort.
I found also this article:
Solved: Re: Power BI Report Server Scheduled Refresh Bottl... - Microsoft Fabric Community
and
Analysis Services thread pool properties | Microsoft Learn
where I can play around with Affinitygroups and thread definitions. But how to find out which ThreadPool is the problem?
Maybe someone got already that deep in configuration of analysis service, and can give a hint how to proceed and if it makes sense here to investigate deeper.
Maybe the only chance is to throttle by maxQueueThreads, but I would like to have the optimal throughput of refreshing reports after the daily load of the DWH is done. And hard throtteling on the number of refreshes.. dont know.. Sounds like a workaround as well.
regards,
Stefan