3 Replies Latest reply: Jan 29, 2015 9:53 AM by Alexander Karlsson RSS

    Qlikview Object Extension Performance

      Dear all,

       

      I have an application that has millions of rows over 30+ dimension. I would like to load them into a Qlikview Extension object. Yet the performance is rather slow. I have tried altering the Page Heigth to 1 and even then it slows everything down.

      My question is: "Is all the data from the dimensions sent to the extension object invariant of the value set by Page Height?"

       

      Thank you,

       

      Ben

        • Re: Qlikview Object Extension Performance
          Alexander Karlsson

          Hi Ben,

           

          No, the page height will define how much data is sent over the wire to the extension.

          However it is very likely that your extension ends up behind something else in the paint cycle and has to wait on its turn to re-paint itself.

           

          Try creating a totally empty sheet and place the extension on it and do some selections to see if the problem still exists.

           

          However if you have a expression exposed to your extension that aggregates tons of data on the server then yes it might need some compute time on the server but the data that will be transferred from QVS to your extension is still defined by the PageHeight property.

            • Re: Qlikview Object Extension Performance

              Hi Alexander,

               

              Thank you for the response. This clarified some things. It was in fact the amount of data that was slowing it down.

              As a side question: "is there a way to define which elements get painted first" so that the data-heavy components get drawn last?"

               

              Thanks

                • Re: Qlikview Object Extension Performance
                  Alexander Karlsson

                  Not really, however most of the objects in the AJAX client renders very quickly.
                  Most charts are actually images that gets generated on the server and then sent over to the client so that is fairly fast.

                   

                  Tables dont render all the content up front but page in the data as you scroll through them.

                  Pivot Tables however are quite intensive however.

                   

                  However it is always a balance, I have come across apps that had over 500 objects on a single sheet (usually someone that reinvented the tabrow with text objects) and that will obviously slow things down.