Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Expectation of Response Time

I know this is a terribly open question, and one not easily quantified, but what is a reasonable expectation for a response time of objects in a QV document?

I have a 2.5 gig document that I load from qvd's. I've got binary flags all over the place, set analysis everywhere, and I join tables together whenever I can. I wouldn't consider my document to be slow, as most sheet objects come back under 10 seconds. But the things I'm working on now are taking anywhere from 20 seconds up to a minute to bring back values, which makes the business say..."Oh it's too slow".

Are my expectations too high? Are others out there experiencing one second response on documents larger than mine? Should objects come back under 5 seconds, or are there folks out there where processing goes into the minutes.

Help me set my expectations.

4 Replies
disqr_rm
Partner - Specialist III
Partner - Specialist III

Yes, I would think 5 seconds are sufficient for most of the charts to work, unless you have a straight table with 1000s or rows.

Are you doing any calculations on the chart itself in the expressions and may be enable conditions?

But again, this situation completely depends on your data model and data contents.

Not applicable
Author

Yep, I do a lot of calculations in the expressions, most of them division and we have many sheet objects with thousands...sometimes 10's of thousands of rows. I set the qvd's up with any calcs of addition and subtraction where I can so I only sum the field, but we have many expressions that require the sheet object to calculate the values.

disqr_rm
Partner - Specialist III
Partner - Specialist III

Wow! for those many rows in a table, I can think of some delay. You may want to find a way so you can split those records in 2 (or more tables based on what makes sense for your requirements.

Not applicable
Author

I'm not sure why I'd do that. My requirements are to build a document that brings in our entire database and calculates any expression in less than 10 seconds. My main table is around 40 million rows. Why create more tables??? I thought from reading other posts that you want to eliminate tables and joins..not make more?