5 Replies Latest reply on May 3, 2017 6:41 PM by Jeff Strauss

    Stats for load times

    Jeff Strauss

      In my pursuit of "most excellent render times", I am looking closely at the built-in "stats for load times".  For this screenprint, the average is about 7 seconds which is pretty good.  Though there are some outliers with the highest being 34 seconds.  Is there weirdness in load times if my users do activities such as having multiple browser Tableau sessions, undock their laptop in the middle of rendering, etc, etc?  I am hoping this is one such explanation and hopefully there aren't too many of these outliers that would drive averages up.  Any automatic way of excluding them?



        • 1. Re: Stats for load times
          Toby Erkson

          Jeff Strauss wrote:

          ...  Any automatic way of excluding them?

          Or simply just identifying them?  I doubt interruptions (e.g. undocking laptop) would be captured by the Tableau Server but maybe the burp would register in a log?  Or maybe only if it were in DEBUG mode would such detail possibly emerge?


          I agree, it would be nice to know more detail for such outliers.  Was it a one-time thing?  Does it happen at a certain time/date?  Maybe it's a db issue, not a Tableau one?  etc.

          • 2. Re: Stats for load times
            Jeff Strauss

            I will do more investigation within my dev system today to see what may be able to be deciphered.  It doesn't appear to be a 1-time thing, no pattern on date/time and it's all extract based.

            • 3. Re: Stats for load times
              Yuriy Fal

              Hi Jeff,


              Suspect that dots on a view are only the "Access View" actions,

              not sure about the subsequent bootstraps (not to mention failures).

              Besides, cache hits constitute the majority of the lower quartiles,

              so the median value could be taken with the grain of salt. imho.


              That said, I'm a little bit skeptical about the real value of this view

              regarding the performance of the views / dashboards being captured.




              • 4. Re: Stats for load times
                Jeff Strauss

                I did a bit deeper analysis based on today's data.  And I found the following.  I am going to talk with one of the users this afternoon and see if we can predictably replicate.


                - The data within http_requests is a combination of retrieve and bootstrap request.  I believe the view computes render times based on the bootstrap.

                - It's an embedded view

                - There's multiple requests for the same user, same vizql session

                - Things start to go astray when there's overlap of requests


                • 5. Re: Stats for load times
                  Jeff Strauss

                  I met with the user that create all the parallel requests.  Basically, his business app has a bunch of tabs on it (darn it, I should have gotten a screenprint).  Each tab has a different client_id, and there are 8 total.  And he switches rapidly between the tabs which each have the dashboard, and the client_id is unique and is passed into the dashboard.  Maybe there's some kind of constraint with the dataengine, I really don't know.  I just know that there's all kinds of undocumented settings within workgroup.yml and I also know that I'm not reaching cpu stress, ram stress, disk stress (at least according to my performance dashboards).