Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Accepted Solutions
How often do you reload documents? If you do not have a Publisher you need to take in to account the impact of reloads on your system.
1GB is not massive. We have documents of 8GB.
"Approx..All the doucments are used by end users regularly." How regularly? At least once an hour, day, week?
"So you mean, i should increase the RAM 85-90% of existing 380gb."
I mean you can tweak the working set low as per below. I think the default is 70%. This is the amount of the Servers RAM that QVS Process can use. If you set this to 70% then 114GB would be left for whatever else on the server requires RAM. You need to analyse what you memory requirements are for other processes but for example setting Working Set Low to 90% would still leave 38GB for everything else on the server.
This would mean you are making better use of your servers memory but it will not necessarily fix your issue. Please do not focus too heavily on memory / hardware, this is an easy trap to fall in to.
I would not recomend adding more RAM. This is unlikely to improve user performance! This sounds more like an issue with the document design. Again what does your dashboard look like? Are there many charts and objects visible on 1 sheet?
Check the basics though first. Go to task manager and see what CPU and Memory utilistation are like. Restart QVS and measure how long it takes for the size of the QVS process to get up to Work Set Low level. If you want to do this properly set up Perfmon to collect the following metrics:
\LogicalDisk(D:)\Avg. Disk Bytes/Transfer
\LogicalDisk(D:)\Avg. Disk sec/Read
\LogicalDisk(D:)\Avg. Disk sec/Write
\LogicalDisk(D:)\Current Disk Queue Length
\LogicalDisk(D:)\% Free Space
\LogicalDisk(D:)\Free Megabytes
\Memory\% Committed Bytes In Use
\Memory\Available MBytes
\Memory\Page Faults/sec
\Memory\Pages/sec
\Memory\Pool Nonpaged Bytes
\Memory\Page Reads/sec
\Network Interface(*)\Bytes Total/sec
\Network Interface(*)\Current Bandwidth
\Paging File(_Total)\% Usage
\PhysicalDisk(_Total)\% Disk Time
\PhysicalDisk(_Total)\Avg. Disk Bytes/Transfer
\PhysicalDisk(_Total)\Avg. Disk Queue Length
\Process(QVDistributionService)\% Processor Time
\Process(QVDistributionService)\Private Bytes
\Process(QVDistributionService)\Thread Count
\Process(QVDistributionService)\Virtual Bytes
\Process(QVDistributionService)\Working Set
\Process(QVDirectoryServiceConnector)\% Processor Time
\Process(QVManagementService)\% Processor Time
\Process(qvs)\% Processor Time
\Process(QVDirectoryServiceConnector)\Private Bytes
\Process(QVManagementService)\Private Bytes
\Process(qvs)\Private Bytes
\Process(QVDirectoryServiceConnector)\Thread Count
\Process(QVManagementService)\Thread Count
\Process(qvs)\Thread Count
\Process(QVDirectoryServiceConnector)\Virtual Bytes
\Process(QVManagementService)\Virtual Bytes
\Process(qvs)\Virtual Bytes
\Process(QVDirectoryServiceConnector)\Working Set
\Process(QVManagementService)\Working Set
\Process(qvs)\Working Set
\Processor(_Total)\% Interrupt Time
\Processor(_Total)\% Processor Time
\Processor(_Total)\Interrupts/sec
\QlikView Distribution Service\*
\QlikView Management Service\*
\System\Context Switches/sec
\System\Processor Queue Length
\Web Service(_Total)\Bytes Total/sec
\Web Service(_Total)\Current Connections
\Web Service(_Total)\Total Method Requests/sec
\Web Service Cache\File Cache Hits %
\Web Service Cache\Kernel: URI Cache Flushes
\Web Service Cache\Kernel: URI Cache Hits %
\Web Service Cache\Kernel: URI Cache Misses
Are the slow responses all the time? Or only at times of High Memory or High CPU utilisation? Expect spikes in CPU but not running constantly high. QlikView is an "In Memory" application so no matter how much memory you give it, it will use it eventually. You need enough for you Documents base footprint and a bit more for cached results. If memory running out / high causes an issue you can manage this with QVS Restarts or Cache Flush, but I don't believe this is the cause of your issue.
Your issue sounds more like poor document design. Are all Documents slow? Or just certain ones? Can you create a new tab of a large document with 1 simple chart and see if that tab is slow to load? You need to narrow down the cause of your issue by process of elimination.
