MENU
A system administrator looks in the QMC > Status > QVS Statistics No documents are open in the QlikView Server but the memory usage of the QlikView Server (QVS) process is still above 10 GB.
Which is the cause of this behavior?
Suggested Answer: B, E
Get Premium QV12SA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
MO
Mona
11 months ago
I disagree with D, the hypercube cache usually clears out.
ST
Stevie
11 months ago
Wait, how can memory be that high with no docs open? Sounds odd!
DI
Dierdre
11 months ago
C seems plausible, high timeout settings can cause issues.
CY
Cyril
11 months ago
I think it’s B, reloads can hog memory for sure.
KI
Kimberely
11 months ago
Definitely A, cached data can stick around.
XU
Xuan
12 months ago
The Object Calculation Time Limit seems a bit off to me. I don't recall it affecting memory usage like that, but maybe I'm missing something.
AM
Amie
12 months ago
I feel like we discussed the Document Timeout setting in class. If it's set too high, could that really prevent documents from unloading?
KE
Keneth
12 months ago
I'm not entirely sure, but I think if a reload is running, it could definitely use up memory until it's done.
BL
Blossom
1 year ago
I remember something about cached data being held in memory to speed up future calculations. Could that be the reason here?
OD
Odette
1 year ago
Ah, I see. This is likely due to the way QlikView Server caches data or handles reloads. I'll need to focus on those potential causes and see if I can determine the right answer.
JO
Joseph
1 year ago
I think the key here is to understand how the QlikView Server manages memory and what could be causing it to remain high even with no documents open. I'll need to carefully consider the options and try to identify the root cause.
CE
Cecil
1 year ago
I'm a bit confused by this one. The memory usage being high with no documents open doesn't seem right. I'll need to review the options and try to figure out the most likely cause.
KR
Kristofer
1 year ago
Okay, let's see. If no documents are open, it's likely that the memory usage is due to cached data or a reload that's still running. I'll need to look into those possibilities.
JE
Jess
1 year ago
Hmm, this is a tricky one. I'll need to think carefully about the different options and the potential causes of the high memory usage.
TH
Thaddeus
1 year ago
I bet the system admin is scratching their head, wondering 'Where did all my memory go?' Time to do some serious QlikView troubleshooting!
KE
Keneth
1 year ago
Haha, the QlikView Server must be really hungry, eating up 10 GB of memory! I wonder if it's going on a document binge.
VI
Vicki
1 year ago
C) The Document Timeout setting is too high, which causes documents to never time out and unload
ST
Stephane
1 year ago
B) A reload is currently running that uses memory in the QlikView Server until it is finished
AS
Asuncion
1 year ago
A) Cached data for unloaded documents remains in memory to decrease calculation time
CA
Caprice
1 year ago
Hmm, I'm not sure. C and D both sound plausible too. This is a tricky one!
DE
Dean
1 year ago
C) The Document Timeout setting is too high, which causes documents to never time out and unload
VI
Vilma
1 year ago
B) A reload is currently running that uses memory in the QlikView Server until it is finished
AL
Alexis
1 year ago
A) Cached data for unloaded documents remains in memory to decrease calculation time
NO
Noelia
1 year ago
B seems like the correct answer. If a reload is running, it would definitely use a lot of memory on the QlikView Server.
PO
Polly
1 year ago
It's possible, but I still think B is the most likely cause in this scenario.
WI
Willis
1 year ago
But could it also be A) Cached data for unloaded documents remains in memory to decrease calculation time?
MO
Moira
1 year ago
That makes sense, a reload would definitely use up a lot of memory.
VA
Valentine
1 year ago
I think it's B) A reload is currently running that uses memory in the QlikView Server until it is finished.
WA
Walton
2 years ago
I think the answer is A. Cached data for unloaded documents remains in memory to decrease calculation time. That makes the most sense to me.
HI
Hildred
1 year ago
User 2: That makes sense. It's important to optimize memory usage in the QlikView Server.
PA
Pamella
1 year ago
User 1: I think the answer is A. Cached data for unloaded documents remains in memory to decrease calculation time.
DE
Denny
2 years ago
I'm not sure, but I think it could also be B) A reload is currently running that uses memory in the QlikView Server until it is finished.
GE
Gerald
2 years ago
I agree with Lavelle. It makes sense that cached data would still be in memory even if no documents are open.
LA
Lavelle
2 years ago
I think the cause might be A) Cached data for unloaded documents remains in memory to decrease calculation time.