Home > Software > Tableau
Interview Questions   Tutorials   Discussions   Programs   Videos   Discussion   

Tableau - What are the possible reasons for slow performance in Tableau?

asked SRVMTrainings August 6, 2014 01:42 PM  

What are the possible reasons for slow performance in Tableau?


2 Answers

answered By   0  
There are some of the reason:

1) Creating a query that returns a large number of records from the underlying table(s), when a smaller number of aggregated records would suffice.You can check this by looking in the lower-left corner of the Tableau Desktop workspace and looking at the number of marks. If this number is very large, you are potentially pulling a large amount of data from the database

2) Use native driver : Tableau will recommend or require you to create a data extract to continue working with a particular driver.Usage of native driver instead ODBC connections as it will generally provide better performance.

3)Test with another tool: A good way to determine if a slow workbook is being caused by a slow query is to test the same query in another tool, such as Microsoft Access or Microsoft Excel.
To find the query being run, look in Aditya kommu\My Tableau Repository\Logs and find a file titled log.txt. Open this file and scroll up from the bottom until you find a section like the following:
The section between the begin and end query tags is the query that was passed to the database. You can copy this text and then use it from a tool like Access or Excel. If it takes a similar time to return as in Tableau, then it's likely the problem is with the query, not the tools.

4)Use extracts : Create a tableau extract if you having perfomance issues.
These extract files can include performance-oriented features such as pre-aggregated data for hierarchies and pre-calculated calculated fields (reducing the amount of work required to render and display the visualization).

FOR  DBA point:
1)Tune your indexes :Make certain you have indexes on all columns that are part of table joins
  • Make certain you have indexes on any column used in a filter
  • Explicitly define primary keys
  • Explicitly define foreign key relationships
  • For large data sets, use table partitioning
  • Define columns as NOT NULL where possible

2 )Use statistics Databases engines collect statistical information about indexes and column data stored in the database. These statistics are used by the query optimizer to choose the most efficient plan for retrieving or updating dat

3 )Optimize the data mode :beneficial to create summary tables if most of your queries only need aggregated data - not base level details records.

   add comment

answered By   0  
One of the reasons is that filters may not be defined appropriately at report level
due to which the entire dataset is pulled from the query (which may not be necessary).
   add comment

Your answer

Join with account you already have



Ready to start your tutorial with us? That's great! Send us an email and we will get back to you as soon as possible!