3 Replies Latest reply on Aug 17, 2016 10:25 AM by Dmitry Chirkov

    tableau size , speed and aggregations

    John Henry

      I've been hearing conflicting statements on how much records / data size, tableau can handle. In the last week two people have told me they have dashes which are, 100m and 600m records. They do incremental refreshes. The dash's are quite quick according to them.

      If I have a dash with xxx million records. Do clients only receive the data that is in their aggregated view.

      So, if I have a source with 200million records. In the dash it shows the aggregated total per week per product. Let's say this is 400 cells(underneath it's millions of records). Is the client only receiving 400 data points.

      Also, if I then add a filter, does the client also receive the aggregated data as per the filter values. So, to continue the previous example, if there was a filter for subcategory, would the client receive a dataset with the aggregation at the subcategory level (let's say 4000 records).


      Essentially I'm asking if it is possible to have a very large extract with incremental refresh which will load quickly(due to having a simple view to the clients using the dash)?

        • 1. Re: tableau size , speed and aggregations
          Dmitry Chirkov
          1. Yes, Tableau only asks data that is required to render dashboard - 400 points (mark on the viz, value on tooltip, filter content - all of them are "points")
          2. Yes, filters are applied before bringing in the data to Tableau
          3. Majority of performance issues with large extracts is a file size itself and time associated with loading it for the first time. Most of the time Tableau has no need to load all of it plus in Tableau 10 we've made several improvements in that area.


          So yes, it's possible to have large extract and fast dashboards. As usual it comes down to complexity of calculations and types of filters applied.

          • 2. Re: tableau size , speed and aggregations
            John Henry

            Hi Dmitry,

            Thanks for the answer.

            Just a couple follow up questions as I'm not entirely clear on your answers.


            1. Regarding the filters. Are you saying that tableau does not transmit the underlying aggregate data. Instead it aggregates the filtered query in the server, then the server transmits the result set?


            2. I didn't ask this in the original query. But, if I have the option to make the underlying data visible (View Data). Would it still just send the 400 data points mentioned above or does it send all the data?


            By any chance do you know of a guide of a web article which discusses designing nice tableau dashes for speed.




            • 3. Re: tableau size , speed and aggregations
              Dmitry Chirkov
              1. Correct. In most cases that's what's happening. Not sure if I understand what's "underlying aggregate data" though. Basically, if on the viz you'll go to Analysis > View Data menu - Summary tab will show you what was pulled from the database.
              2. When you move to Underlying Data (or Full Data) tab - it'll issue different query and will bring a different dataset. This particular query is typically limited to top 10000 rows so it won't be "all the data".
              3. Best Practices for Designing Efficient Tableau Workbooks, the V10.0 edition | The Last Data Bender


              May I ask what's the underlying concern? Load generated on the backend? Billing associated with querying large amounts of data?