6 Replies Latest reply: Mar 24, 2017 1:58 AM by dhasharadh goud RSS

    Any possibility to estimate the response time of the selection in Direct discovery app ??

    dhasharadh goud

      Hi All ,

       

      we developed a PoC on direct discovery and its working fine with some delay in the response time(>10 Sec), now we need to estimate the response time (Query execution time) for the selections that user made to a project.

       

      total SQL DB size is 100 GB and we are planning for 20 Qvw files based on data categories. each QVW will be around 500 MB.

       

      On what basis we can come with such estimates.and also please do let me know if any other method to estimate the time for client level Queries..??

       

       

       

      Best Regards,

      Dhasharadh

        • Re: Any possibility to estimate the response time of the selection in Direct discovery app ??
          Dave Riley

          I've never tried to do this, but I would say it is almost impossible to estimate response times. You need to know how the database is set up (eg is the physical server only used by this application, is it a virtual server), how many concurrent users will be accessing the database, the speed of your network and so on.

           

          You could try to set up a standalone test server and perform a stress test on that.

           

           

          flipside

            • Re: Any possibility to estimate the response time of the selection in Direct discovery app ??
              dhasharadh goud

              Hi Dave ,

               

              Thanks for Quick response , we are creating a view from the database and using that view as our Qlikview source for direct discovery.

               

              our users are planning for a project on the direct discovery concept , but i don't think it is as smooth as normal reporting.

               

              there are many things to consider , Do you know anyone who completed a Qlikview project on direct discovery and using it right now...

                • Re: Any possibility to estimate the response time of the selection in Direct discovery app ??
                  Dave Riley

                  Unfortunately not. However one tip I would give is to avoid as much as possible the use of views in SQL as it will hit the underlying tables just as if you were querying them directly. If this means sharing access with other users and applications, you have probably got your biggest potential delay right there.

                   

                  I would 'replicate' the data into a standalone table to be used solely for this app at the very least, although this would depend on your particular use-case and how up-to-date the data needs to be.

                   

                   

                  flipside

                    • Re: Any possibility to estimate the response time of the selection in Direct discovery app ??
                      dhasharadh goud

                      Hi ,

                       

                      Thanks alot for your time.

                      we are doing a feasibility study for the possibilities for Live reporting in our environment which contain 92 GB of reporting data whereas total size of the DB (SQL) is 300 GB.

                       

                      users expecting the Prefered RAM Size as well as Architectural diagrams by considering Direct Discovery Method.

                       

                      We have many posts in community about Normal Qlikview reporting and Its RAM Sizing , But I did not find any thing related to Direct Discovery related.

                       

                      As am more into developing no idea on these admin related tasks.

                       

                      can you please help me with this.

                       

                      Regards,

                      DG.

                    • Re: Any possibility to estimate the response time of the selection in Direct discovery app ??
                      Peter Cammaert

                      Many community members are using Direct Discovery to their advantage. I'm sure one of them will post his/her experiences with this method of obtaining data sets.

                       

                      Keep in mind that Direct Discovery is not a replacement for the normal QlikView Script-controlled data extraction process. Direct Discovery can be used to speed up the performance of your document in very specific cases, for example when in need of a limited set of transactions from a huge data source based on specific selections in your document. In that case, loading everything beforehand into your QlikView document would make it huge (and possibly sluggish if your server isn't scaled accordingly) while only a limited number of rows is needed at any time.

                       

                      If you try to use Direct Discovery to offload a substantial volume of data rows from one or more data sources, you will face typical database query performance issues, like any other database client. If the code to fill a view is long-running, users will have to wait for the view code to complete before even the first row is transferred. If Direct Discovery needs to transfer a large number of records from the same data source, the DB engine and network may become bottlenecks when multiple users start requesting rows at the same time.

                       

                      Compare this with the high performance in-memory analysis that QlikView offers out-of-the-box whereby all data is present in RAM (the fastest storage medium available at the moment). Direct Discovery is not an end by itself.

                       

                      Best,

                       

                      Peter

                        • Re: Any possibility to estimate the response time of the selection in Direct discovery app ??
                          dhasharadh goud

                          Hi peter, Thanks alot for your time.

                           

                          we are doing a feasibility study for the possibilities for Live reporting in our environment which contain 92 GB of reporting data whereas total size of the DB (SQL) is 300 GB.

                           

                          users expecting the Prefered RAM Size as well as Architectural diagrams by considering Direct Discovery Method.

                           

                          We have many posts in community about Normal Qlikview reporting and Its RAM Sizing , But I did not find any thing related to Direct Discovery related.

                           

                          As am more into developing no idea on these admin related tasks.

                           

                          can you please help me with this.

                           

                          Regards,

                          DG.