1 of 1 people found this helpful
Rohan - I have also contacted Russell to see if he can assist with this. Thank you for the question.
3 of 3 people found this helpful
Short answer? I don't know. Sorry - I haven't kept up with it. I think you should be able to figure this out yourself without too much trouble. though:
- Create a dashboard and add your "big" view first, then a small view - Execute and see which fires first
- Create another dashboard and add a "small" view first, then the big one - Execute and see which fires first.
Thanks Russell Christopher I did what you said and here are my findings:
- Due to Tableau Query Batching, it itself see which query to run first.
- As all the views are from same extract, NO PARALLEL QUERY EXECUTION
- Each view is running two queries every time.
- One for getting aggregated records depending on the dimension.
- Second just aggregated data without any dimension(Amazing thing is for few views we are not even showing "Totals" even then it's doing). Is it possible to make Tableau NOT to run this query when not needed?
Hey Rohan -
There really is no way to control how Tableau chooses to batch and execute queries.
Let's take a step back, however. It seems like you are doing all this work because you are trying to make a "slow" dashboard faster, correct? Based on what you've explained, it sounds to me as if you simply have too much stuff (vizzes, filters) in each dashboard. It also sounds like your expressions and calculations are fairly complex (nested).
Of the questions you've been asking really address the symptoms of "slow" vs. the cause. Have you considered simply refactoring the dashboard itself and making it better vs. hoping that you can improve things on server via "smoke and mirrors" of caching, etc?