{"id":4879,"date":"2019-04-09T09:17:56","date_gmt":"2019-04-09T09:17:56","guid":{"rendered":"https:\/\/www.gigxp.com\/?p=4879"},"modified":"2020-04-13T07:01:39","modified_gmt":"2020-04-13T07:01:39","slug":"powerbi-report-server-performance-tuning","status":"publish","type":"post","link":"https:\/\/www.gigxp.com\/powerbi-report-server-performance-tuning\/","title":{"rendered":"PowerBI Report Server Performance Tuning Best Practices (PBIRS)"},"content":{"rendered":"

In this article, we are going to highlight the PowerBI<\/a> Report Server performance tuning<\/strong><\/em> best practices. Since the PBI report server is an enterprise reporting<\/a> solution, it is imperative to optimize the performance<\/a> of the overall server.<\/p>\n

Microsoft has done their own benchmarking<\/a> where less than 5% of the users are consuming the same report at the same time. The results are below: As you can see from the results, the PBIX reports (PowerBI Desktop) consumes more resources and offers significantly less performance on an 8 CPU, 32 GB memory server. On the contrary, when you double the resources (16 CPU & 64 Gigs of RAM), the performance gap considerably reduces.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Workload Bench<\/strong><\/td>\n8 Core & 32 GB RAM<\/strong><\/td>\n16 Core & 64 GB RAM<\/strong><\/td>\n<\/tr>\n<\/thead>\n
Power BI Report Heavy (PBIX)<\/strong>\u00a0(>60%)<\/td>\n1,000 users<\/td>\n3,000 users<\/td>\n<\/tr>\n
Paginated (RDL) Report Heavy (SSRS)<\/strong>\u00a0(>60%)<\/td>\n2,000 users<\/td>\n3,200 users<\/td>\n<\/tr>\n
PBIX Heavy Reports<\/strong><\/td>\n50 Concurrent user loads<\/td>\n150 Concurrent user loads<\/td>\n<\/tr>\n
SSRS Heavy Reports<\/strong><\/td>\n100 Concurrent users<\/td>\n160 Concurrent users<\/td>\n<\/tr>\n
PBIX Heavy Reports (Total User base)<\/strong><\/td>\n1000<\/td>\n3000<\/td>\n<\/tr>\n
SSRS Heavy Reports (Total User Base)<\/strong><\/td>\n2000<\/td>\n3200<\/td>\n<\/tr>\n
\u00a0View the Report uses as a reference<\/strong><\/td>\n8 core<\/a> (PBIX)<\/p>\n

8 core<\/a> (SSRS)<\/td>\n

16 core<\/a> (PBIX)<\/p>\n

16 core<\/a> (SSRS)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

As you can see from the official tests, the performance of the report server significantly increases when you increase the allocated memory and RAM. However, do note that this is a 3-tier server and comprises of the following:<\/p>\n

    \n
  1. AD Domain Controller (2 Cores, 7 GB RAM – DS2_v2)<\/li>\n
  2. Database Server (15 Cores, 56 GB RAM – DS5_v2)<\/li>\n
  3. SQL Server Analysis Services (15 Cores, 56 GB RAM – DS5_v2)<\/li>\n
  4. PowerBI Report Server (Standard_D8S_v3 for 8C\/16 – Standard_D8S_v3, GB & 16C\/64GB, vStandard_D16S_v3)<\/li>\n<\/ol>\n

    Now, these are all Azure Virtual Machines<\/a>, and PowerBI report server is primarily meant to be run on-premises. So, for on-premises deployment, let’s find out what best practices you need.<\/p>\n

    \n
    \n

    Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n