Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all,
Some of my user of one QV appli find that is to slow when they make selections. Indeed, they have to wait approximately 1,5 seconds after each selection.
So i wonder in which proportion adding RAM on their computers could improve fluidity during sélections. They have 4 Go RAM.
Regards
Hi Jean,
To my knowledge, I would suggest you to check if there are any time-consuming calculations or charts that have involved major complex functions in the UI. Because if in case there is a huge volume of data in the dashboard and we make some selections, to re-calculate the chart values it might take some time.
If all the calculations are optimal, then try to analyse Memory usage in the access point server( server having QlikView Server Service installed), in case if the user is using the source document (not a published one) then try to increase his machine RAM.
Thanks for your reply Ravindra. I'll try to chek time-consuming calculations with Document Analyser Document Analyzer V3.0 Update Available. I think this app is able to do that.
I think i'am far to have a huge data volume, but it begins to weight a bit (.qvw 950Mo, 50 million records).
Hi,
What is size of your App?
Hi, 950 Mo.
PFA
Update:
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%
Hi,
can you tell how your user accessing qv application??
using access point then you need to increase ram of server where qv application is published.
Try below suggestion also
1: You can try preload from QMC
2: Optimise your dashboard,
3: avoid complex expression on front end try to move it in your script.
4: avoid synthetic key.
Regards,
Prashant
Hi Prashant,
1: You can try preload from QMC
What do you mean with preload QMC?
2: Optimise your dashboard,
You mean limit number of charts/graphs?
3: avoid complex expression on front end try to move it in your script.
I have classical set analysis expressions, but enclosed in if for test if user has selected the current month or pasts month. If it's current month i use a flag in my SA. Not sure it has a big effect.
4: avoid synthetic key.
I don't have synthetic key.