1 of 1 people found this helpful
Optimization is such a broad topic and dashboard poor performance might be caused by several factors which might be unique for different people. So, it could be a challenge to generalize a solution.
Having said that, the first thing to check is if the dashboard loads faster on Tableau Desktop than on the Server. If it does, then the problem might be more related to the server. It took less than 2 mins to open on my system, I don't know how the Desktop version performs on your system.
The next thing to look at is your infrastructure. Is your Tableau server housed in it's own hardware or is it sharing hardware with other applications? This could determine how much resource is available to Tableau server. You mentioned that you are currently on the 8 core CPU and 32GB memory plan. I noticed that this plan could be upgraded to 16 Core/64GB plan for a marginal cost. However, if your Tableau server doesn't have it's dedicated hardware, then I don't know how much this will be of help.
The other important thing to look at is the workbook itself. Hide unused columns, delete unused worksheets. Remove rarely used filters. COUNTD() and LODs kill performance in pre 10.5 versions. However, Both calculations have not been intensively used in your workbook. The only thing I noticed is that there are few calculations with multiple-condition IF statements. It may take Tableau some time trying to go through all the conditions before the views are rendered. Hopefully, version 10.5 with the new hyper technology might make a difference. You can use the performance recorder to test different elements of your workbook. Record and Analyze Workbook Performance .This link contains other links 6 Tips to Increase Dashboard Performance
Your datasource is relatively small and I don't see much issues with 16k rows of data. However, if everything fails, consider moving the Excel workbook as a table to a SQL database using an ETL process which will refresh on a regular basis. Then consider using an extract instead and moving some heavy calculations to the database.
Hope this helps.
Hi Okechukwu -
Thank you so much for your thoughtful and detailed response. I was pulled onto another project but am now back and onto problem-solving this issue. I deeply appreciate the resources. I think I am going to have to do some slashing, but at least I am doing it knowing that I've tried every other options.
You're welcome Kimberly. Gad it helped.