Professional Documents
Culture Documents
QlikView Publisher Sizing
QlikView Publisher Sizing
Version
Date
Author
1.0
08 September 2014
Shane M Spencer
PUBLIC
Contents
Introduction ............................................................................................................................................ 3
QlikView Distribution Service (QDS) & QlikView Batch (QVB) ................................................................... 4
Concurrent / Simultaneous Reloads & The Reload Process ...................................................................... 4
Disk, RAM & CPU Requirements .............................................................................................................. 6
Sizing Your (Publisher) Server .................................................................................................................. 7
Memory Metrics...................................................................................................................................... 8
Network Metrics ................................................................................................................................... 10
Process Metrics ..................................................................................................................................... 11
Key QlikView Processes ......................................................................................................................... 12
Web Server Metrics ............................................................................................................................... 13
Other Metrics ........................................................................................................................................ 14
List of Perfmon Counters ....................................................................................................................... 15
Perfmon Data Collector Template.......................................................................................................... 17
PUBLIC - Page 2 of 7
Introduction
Correctly sizing the Publisher Server seems to be something that is overlooked, or at best based purely
on guess work. However, it is important to understand your requirements so that your server has
enough capacity (but not large amounts of excess) and to ascertain if you should have a dedicated
Publisher Server or whether it can reside on the same physical machine as QlikView Server.
The size of the QlikView Publisher will depend on several factors: the size of the data being loaded; how
the data is loaded / document design; the number of Documents being reloaded; the number of
concurrent tasks being run.
PUBLIC - Page 3 of 7
PUBLIC - Page 4 of 7
PUBLIC - Page 5 of 7
Disk Requirements
As a reloaded document is being written to disk it does not over-write the existing document until the
process is complete. That means there must be enough free capacity on the disk (where the document
is Distributed to) to temporarily write the document to; once the write is complete the space consumed
by the older version of the document will be released.
An incorrectly sized environment is likely to use the Paging File (Disk that is used as Virtual Memory) so
there should be enough Disk space to allow this to grow also.
RAM Requirements
Whilst a Task is being executed a corresponding QVB process will be consuming Memory. The amount it
will consume will depend not only on the amount of data being loaded but also the design of the
document (as temporary tables may be created).
For example we have observed the following:
A QVW of 6.25GB consumes about 25GB of RAM when loaded in to Memory of the QlikView Server. The
reload process (QVB) for this same document (temporarily) consumes about 47GB of RAM at its peak. A
pre-requisite task that consolidates about 2 months of data in to QVD(s) consumes well over 100GB (and
runs for over 5 hours) when we streamlined the task to run quicker we shaved 45 minutes off the batch
but peak Memory consumption was about10-20GB more.
If there is not enough available Memory (RAM) for the reload Task(s) then Windows Server will
automatically start using the Paging File (Disk that has been allocated as an extension to the servers
virtual Memory). This is extremely bad, especially for In Memory applications such as QlikView, as
reading from Disk is 1000x slower than Memory.
CPU Requirements
Whilst a Task is being executed a corresponding QVB process will be consuming CPU. Insufficient
resources will mean Tasks are queuing for Processor (CPU) time.
PUBLIC - Page 6 of 7
n.b. To estimate your base Memory footprint requirements (of QVS) excluding cached results, multiple
the size on disk of you individual documents by 4.25. A more detailed analysis will need to be done to
understand the amount of memory QVS requires to support user activity but thats another story
PUBLIC - Page 7 of 7