10 Replies Latest reply on Apr 22, 2017 3:00 AM by Yuriy Fal

    when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.

    porntip Tathikun

      How to configure to improve perfermance.

        • 1. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
          Nick Bachofen

          Can you provide any additional information? What is slower...how do you know it is slower?

           

          I would assume your dashboards are running slower...what data source are you using...have you looked at performance recording: Create a Performance Recording

          • 2. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
            Mark McGhee

            There were some issues with Data Engine performance for earlier versions of 10.1.x that had some fixes in 10.1.5 and more in 10.1.6.   If a number of your dashboards are extract dependent, would strongly recommend upgrading to 10.1.6 (and actually we have 10.1.7 out as of this writing).   If after upgrading you're still experiencing issues would recommend opening a support case:  Support Case | Tableau Software

            1 of 1 people found this helpful
            • 3. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
              Jeff Strauss

              Mark McGhee thanks.  can you fill in the blanks a bit more so that we can quantify how much we may be effected?  It's not a simple task for us to upgrade and need to make a case to our leadership to invest the time / resources for a tangible benefit.

              • 4. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
                Mark McGhee

                We have the following KB article which hasn't been out too long:

                 

                Data Engine Performance Issues After Upgrading Tableau Server | Tableau Software

                 

                In addition, for some customers we have seen simply republishing a workbook can bring the render time back to an acceptable level though there are no guarantees this would help.  Also, that could be quite cumbersome if your organization has thousands of workbooks.

                 

                Ideally if you were able to update a non-Production environment first and do some performance testing on workbooks that you know were rendering slowly that may help to give you an idea if upgrading to a higher maintenance release of the 10.1.x branch would be helpful

                2 of 2 people found this helpful
                • 5. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
                  Jeff Strauss

                  Mark McGhee

                  Thanks for the very useful KB article.  If we upgrade to 10.1.7 or 10.3.x (whenever this becomes available), then will we need to setup multiple dataengines (per node), and "tabadmin set dataengine.optimize_icu true" options?

                  • 6. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
                    Mark McGhee

                    For the "dataengine.optimize_icu" setting we did already enable it by default starting with April maintenance releases.  It's kind of easy to glance over when reading through the KB article but it's really the one line:

                    ------------------------

                    For 10.0.5-10.0.8 and 10.1.3 - 10.1.6, please run steps below for optimal performance. This option is enabled by default after these versions.

                     

                    So 10.1.7 should already have this enabled.  You can output Tableau Server settings to verify with something like "tabadmin config -o output.txt" then look to see if that setting is true/false to verify.

                     

                    You could try bumping up the number of data engines though again, would be best to try out in non-Production environment first if possible.   If the issue only occurs in Production, you could still try to bump up the number of data engines but the system should be closely monitored after making the changes. 

                     

                    Our KB articles do get updated on a periodic basis so if at some point additional data engines aren't recommended I would think it will get called out.

                    • 7. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
                      Jeff Strauss

                      we're already running 2 dataengines on worker1 and worker2, and I was in fact getting set to reduce it down to 1 because I thought it was causing problems, but now I'm pretty much content to leave it alone at least for now.  I will try the tabadmin set... with our dev 10.1.3 then prod 10.1.3 to see what happens.

                       

                      With this being said, our next upgrade will most likely be 10.3.x, and it would be really nice to have some clear guidance via the admin guide of how many dataengines / dataservers to allocate per node.

                      • 8. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
                        Yuriy Fal

                        HI guys,

                         

                        As a recent TDA => TSA convert,

                        i'd like to share my tiny experience.

                         

                        A case would be a "well-balanced"

                        single-node instance carrying a mix of

                        mostly light views (live connections to Vertica)

                        and a couple of extract-heavy ones

                        incrementing hourly through the day.

                         

                        And it looks like the load from these heavy dashboards

                        would throttle the data engine, bringing the node into

                        a totally unresponsive state for some 15-30 minutes.

                         

                        the behaviour is fairly consistent --

                        with or without backgrounders at play.

                         

                        Fortunately, I've found this thread and catched up.

                        Two copies of data engine and the ...icu stuff woul be of great help.

                        The node is behaving nice right from the start,

                        CPU usage is about 50-70% under the load.

                        But the throttling still occurs, albeit later then before.

                         

                        I've been playing with dataengine.query_parallelism

                        as well as native_api.connection.limit.dataengine

                        config params, but gave up soon and revert to defaults.

                        (BTW, I'm still not sure about the default value for the latter :-)

                         

                        I can see a much better "smoother" behaviour with Alpha 3 --

                        both on Linux and Windows with just one copy of data engine

                        (HyPer stuff I guess?).

                         

                        So my hope is having this nasty little problem

                        the he distant past (in the very near future).

                         

                        Yours,

                        Yuri

                        1 of 1 people found this helpful
                        • 9. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
                          Jeff Strauss

                          Hi Yuriy.  What version of TS are you running?  I ask because I am interested to know if the ICU parm even will have any effect on my installed prod version 10.1.3, And I ask because usually I see all the available default settings in workgroup.yml and tdeserver_standalone.yml, but this particular one is nowhere to be found within 10.1.x so I wonder if it will have any effect for me or not.  I know when I run the tabadmin set it will add it to workgroup.yml but there can be any custom setting added without really doing anything effective (i.e. "tabadmin set friday 0").

                           

                          And BTW, we are running 2 dataengines on two of our workers already, I was getting ready to lower it to 1, but I'm backing off and for now it's going to stay at 2.  And we are seeing occasional spikes on the tdeserver process that causes CPU intermittently to go up to 100%, but maybe the icu setting will help.  I'd sure like to know more of what it does first though.

                           

                           

                           

                          Agreed on the nasty little problem in the rear view mirror...

                          • 10. Re: when upgrade tableau server 9.3.4 to 10.1.4. Why everything very slow than prior release.
                            Yuriy Fal

                            Hi Jeff,

                             

                            This is one of our customers, and they're on 10.2.1 already.

                            They've been upgrading several times (from 10.0.1 and on) --

                            not actually doing a clean install or restore --no-config --

                            so initially there was no such a setting in their config as

                            dataengine.optimize_icu: true

                             

                            With that setting -- and two data engines per node --

                            there is a substantial (positive) difference in behaviour.

                            I'm confident it would be the same for you. No harm.

                             

                            Yours,

                            Yuri

                             

                            PS As Mark mentioned above, a clean install of

                            10.0.9, 10.1.7 and 10.2.1 (and also Alpha 3)

                            would have this setting written in config by default.

                             

                            1 of 1 people found this helpful