We're creating QlikView reports for a client that handles a large volume of phone calls. They need both aggregate and detailed information about their callers, and how the calls were handled. We're having performance problems (timeouts, rendering delays, session disconnects, etc), and getting mixed messages on whether QlikView is intended to be used the way we're using it.
At the detailed level, a table box is used to display individual call records, with a calculation condition to prevent the table from being displayed if selection criteria exceeds a 1000 row limit. A QlikView Extension Object is used on the same sheet as the table box, to select/play recordings of individual calls, using data from the fact table to fetch/play audio from an external server.
My question is whether QlikView should be able to do this type of detailed reporting, with reasonable performance/reliability, if properly sized and configured? Or are we trying to do something it's not really intended for, perhaps functionally, or working with a data size that's too big for what the product can handle, on any hardware?
- The data is in a star schema loaded from a datamart
- The fact table contains about 50 million rows, 50 columns wide, no synthetic keys
- Data is refreshed with hourly incremental updates, preload=On, application qvw file is ~6GB
- Software: QV v11.00/SR2/64b (build 11440), w2k8/SR2 enterprise
- Hardware: QVS=32 cores, 320G ram; QVP=24 cores, 128G ram
Some of the timeout problems occur consistently with only a single user on the system. The system generally performs well with smaller data sizes thru several million rows, but not at the 50M row size. When the problem occurs, server memory/cpu utilization is stable, no significant changes. Users also intermittently experience problems with session disconnects after being idle 10-15 minutes (max inactive session time=30 minutes).
Our QV servers are hosted on dedicated VMs (no other VMs per host) due to operational constraints, but we don't have any evidence that the VM environment is causing the problems, and have seen similar symptoms on non-VM dev servers.
Any insight appreciated!