Hey Niclas -
It's going to be difficult to get guidance without the community seeing your workbook. More often than not, Server Perf issues are caused by workbook design issues. Would it be possible to post?
As Russell noted, it may be related to the workbook design. For example, lots of calculated fields (especially string calculations) can degrade performance. You mentioned that you have 5 charts and a map. Currently, in Tableau 7, all views in a dashboard are processed in sequence (Tableau 8 will allow parallel processing). If any one of the views has an especially poor performing query it can cause the entire dashboard to suffer.
One thing you can do to start eliminating issues is to install Tableau Desktop (even a trial version) on the same machine where Server is installed. If it is still slow in Desktop, you may be looking at workbook design, data connectivity / network issues, resource issues. If performance is fine in Desktop, you may be looking at Server specific configuration issues.
You also should look at each view independently. Is performance poor for all views or specific ones?
If specific ones, do they share something in common (same data connections, lots of marks, lots of calculated fields)?
I am having a similar problem. When I run my workbook through Tableau on my computer, there is about a 3 second delay to update the dashboard visuals which is very good. However when I publish it to Tableau Server the delay is about 8-10 seconds. I can't post my workbook, but does anyone know of common ways to troubleshoot this situation? At this point I almost feel like telling people to download Tableau Reader because its much faster than Tableau Server.
I remember someone (Tracy maybe?) saying not to be too focused/concerned with the CPU activity as it's some normal background processing.
I am having the same slowness issue for tableau server. However, in my case the tableau server slows down only for the graph having GEO map. I have 2 worksheets. one with only bar chart and other one with GEO map. When I publish both the bar chart graph loads preety fast but GEO map takes longer than expected. So i removed all filters from GEO map and kept it as simple as possible (showing only united state names). I published the simple GEO map graph and still it takes longer time.
I can't figure out why only GEO map takes too long to load.
Thanks in advance
1 of 1 people found this helpful
If you aren't using internal maps that means your map display is going out to the internet and getting the map info so networking will be a source of delays.
How are the services setup on your sever. How many of each are you running and what is your current work load.
We're experiencing a severe problem with the responsiveness of the Tableau Server Maintenance dashboards.
All of them - Server Activity, User Activity, View Performance History, Background Tasks, Space Usage, and Customized Views - are extremely slow to respond and frequently fail with a "Session Ended by Server" message dialog containing: "An unexpected error occurred on the server. If you continue to receive the error please contact your Tableau Server Administrator." which isn't really all that useful since I'm the Tableau Server Administrator in an environment where I'm not allowed access to the Windows server Tableau Server is running on.
What version are you on? I just saw these errors for the first time today, we're on 8.0.2.
We're still on 8.0 Getting things upgraded here is very, very difficult and slow.
I'm writing up an email to support now.
You could try to run Sysinternals Process Explorer which provide unique insights of Windows processes and applications behavior and then you could send the logs or screens capture to support team.
Thanks, Christian. I'll pass this along.
Oddly enough, my client is one of the really big global financial institutions and all of its IT infrastructure stuff is strictly off limits to the business, which is where I am. The nominal reason for this is that they're the experts. The effect is that it's very, very difficult to get anything done vis-a-vis real dynamic investigation into what's really going on with the machinery.
The IT group is charged with, and very protective of, guardianship of the machinery. They're the professionals, and one would think that they're up to speed on how to assess the performance of said machinery.
I get it. But a long time ago in very similar conditions we did manage to found what was going wrong using Process Explorer.
Let me guess.... 4 letters who never sleeps?