topic Is qlikview suitable for larger reports? in QlikView

Is qlikview suitable for larger reports?

Anonymous — Wed, 30 Dec 2015 06:43:48 GMT

We have some existing reports where the no of records shown in the table are 50k , but the users are not happy with it for the retrieval time of the records, currently they have pagination in place ...they wanted to try Qlikview ..but not sure if Qlikview is suitable for their needs ...are there options to show more than 50,000 rows in a report? Is this something advisable?

Thank you!

Re: Is qlikview suitable for larger reports?

ajsjoshua — Wed, 30 Dec 2015 06:48:14 GMT

Hi,

Qlikview is verey much suited for larger reports.

When we load the data and store it as Qvd file the retrieval time is very fast,since data is stored and processed in RAM.

Regards,

Joshua

Re: Is qlikview suitable for larger reports?

arulsettu — Wed, 30 Dec 2015 06:50:27 GMT

check this

Qlikview's Maximum data volume

200 million rows is business as usual, with decent performance. Above that, performance degrades quickly if you do "load *; select *".

You can go above 500 million rows, if you optimize the design and can afford hundreds of GB of memory and tens of CPU cores.

this too

optimization techniques for qlikview

Re: Is qlikview suitable for larger reports?

Anonymous — Wed, 30 Dec 2015 07:10:12 GMT

‌my question is more about front end , showing 50k records in straight table or table box.. How is the performance ?

Re: Is qlikview suitable for larger reports?

Anonymous — Wed, 30 Dec 2015 07:15:35 GMT

Are you facing any issue??

Thats true, more data will slow down the process...

But again if your hardware are upto standard and as per data available, you would not face any issue.

Re: Is qlikview suitable for larger reports?

Anonymous — Wed, 30 Dec 2015 07:16:14 GMT

you want to check maximum limit of data for Straight / Table Box?

Re: Is qlikview suitable for larger reports?

arulsettu — Wed, 30 Dec 2015 07:17:42 GMT

its based on your RAM and the expression you used. in my case its running but its taking bit time

Re: Is qlikview suitable for larger reports?

Anonymous — Wed, 30 Dec 2015 07:26:09 GMT

‌yes i want to know the limitation of display .. after how many rows of data u start seeing issues ...

Re: Is qlikview suitable for larger reports?

arulsettu — Wed, 30 Dec 2015 07:31:14 GMT

above 50,000 and object cal time is 17875

Re: Is qlikview suitable for larger reports?

Anonymous — Wed, 30 Dec 2015 07:35:54 GMT

‌17875 what is this number ? Time?min?sec?

Re: Is qlikview suitable for larger reports?

arulsettu — Wed, 30 Dec 2015 07:37:08 GMT

seconds

Re: Is qlikview suitable for larger reports?

tresB — Wed, 30 Dec 2015 07:37:14 GMT

AFAIK, there is no such row-limitation in chart display. I have just tried with 10M rows in a straight table, and it just populated in a fraction of second. However, it would depend majorly on your:

system hardware
chart dimension/expression
no. of columns in the chart

Re: Is qlikview suitable for larger reports?

robert_mika — Wed, 30 Dec 2015 08:03:10 GMT

and for the reporting Qlikview has N-Printing

Introducing QlikView NPrinting | Qlik

Feeling Qlikngry?

How To /Missing Manual(24 articles)

Re: Is qlikview suitable for larger reports?

HirisH_V7 — Wed, 30 Dec 2015 08:24:11 GMT

Hi,

QlikView is designed for gigabytes-scale databases. (More precisely, it’s constrained by how much RAM you can address in a single box, and that’s how the numbers currently work out.) In particular:

QlikTech recommends 2-4 gigabytes of compressed data per core. QlikTech says 10X is a good rule of thumb for compression, although it sounded like that’s a little (not a lot) on the high side when compared simply to raw data.
QlikTech further recommends RAM amounting to another 10% of data size be set aside for each concurrent user (e.g., for cache). However, to say that’s really too pessimistic, and in most cases 5% would suffice.
Bottom line: QlikView “comfortably” handles databases with10-20 gigabytes of compressed data, at whatever product of record count and record length you like. (E.g., 1 billion relatively narrow records.) That’s on the order of 100 gigabytes of raw data.
Indeed, several QlikView customers manage several billion records each.

Hardware Specifications for your server plays a prominent role for Application Performance.

Hope this helps,

Regards,

HirisH

Re: Is qlikview suitable for larger reports?

Peter_Cammaert — Wed, 30 Dec 2015 09:03:08 GMT

I would like to add to the previous that in QlikView, a reasonably small straight table (<50000 rows) might take a while to recalculate and display, while a reasonably large table (>10mil rows) might display instantaneously.

Meaning that as tres says, it's not the technology that limits the performance of a QlikView dashboard, it's what you do with that technology. QlikView is designed and built to handle massive amounts of data. If the dashboard designer doesn't know how to bring this best to fruitition and drops a massive amount of data on a machine with few Gigs of RAM, performance will sink.

Rest assured, QlikView can handle more than 50000 rows with single-second response times.

On the other hand, it's not your typical dashboard design best practice to throw a table with 100000 rows or more in the face of your end-users. So I'm guessing that you intend to produce large amounts of data on-screen to export to Excel, correct?

Peter

Re: Is qlikview suitable for larger reports?

oknotsen — Wed, 30 Dec 2015 09:45:00 GMT

Sounds like milliseconds (as in 18 seconds), as the expressions would have timed out after 60 seconds.

If you have an application with 50k rows that takes 18 seconds to calculate, you must be on very old hardware or having unneeded complex expressions.

I have seen an application with 1700m rows of data give a result in 6 seconds and that was not on the best hardware either.