Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all,
can anyone explain me how qlikview server use the memory when we have severals applications and many user .
Simple Senario :
i have one application with 8GO of size deployed on my server (96 RAM 6 cores ).beside i have 40 users who can acces this application .Let's imagine thats user 1 connect to server .How the mermory is used int his case ?
After deconnecting from the server how the mermory is used also in this case ?
in the case of many users in the same time .how it works ?
how works sign in sign out ?
Thx lot
Hi,
RAM = (RAMuser × No. users) + RAMinitial
Where
RAM〗initial = QVWsizedisk × FileSizeMultiplier; this is the initial RAM footprint for any application
RAM〗user =〖RAMinitial × userRAMratio; this is the RAM each incremental user consumes
QVWsizedisk = SourceData × (1 - CompressionRatio); this is the size, on disk, of a
QlikView file
Assumptions:
userRAMratio: range between 1%–10%
FileSizeMultiplier: range between 2–10
CompressionRatio: range between 20%–90%
Thx for theses explications .
what do you mean by FileSizeMultiplier ? and how we calculate it ?
Hi there,
please see the attached:
Hi there,
please see the attached:
Hi there,
please see the attached:
Hi there,
please see the attached:
thx.
suppose that we have 4.8gb allocted for our application (4 gb of size + 3 user ).
what happened when all the user sign out ?
thx.
suppose that we have 4.8gb allocted for our application (4 gb of size + 3 user ).
what happened when all the user sign out ?
The memory will be released.
You can see that on Task Manager.
The memory will be released.
You can see that on Task Manager.
i'v checked it out ,it's not released .
Are you sure about that ?
Because i'v seen on one of my last project , on the server it was required to have drain down's batch running on .
i'v checked it out ,it's not released .
Are you sure about that ?
Because i'v seen on one of my last project , on the server it was required to have drain down's batch running on .
The process is not immediate.
works like System.GC on C# or System.gc() on java.
The process is not immediate.
works like System.GC on C# or System.gc() on java.
Its released when needed.
Its released when needed.