MENU
A QlikView Server is using more than 93% of its total memory. Users report slow performance when working within a QlikView document. The Working Set Low value is 70% and the Working Set High value is 90%.
What is causing the performance issue on the server?
Suggested Answer: D
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
RO
Rosann
11 months ago
High memory usage usually leads to slow performance, no doubt about it.
MA
Mammie
11 months ago
Wait, are we sure it's not A? Removing PGO files seems risky!
ST
Staci
11 months ago
I disagree, it could be D with the cached results being dropped.
LA
Laurel
11 months ago
I think it's definitely option C, swapping to virtual memory.
CA
Catina
11 months ago
Sounds like the server is overloaded with memory usage.
BU
Bulah
12 months ago
I feel like I've seen a question about PGO files before, but I don't think that's the main issue here. It has to be something with memory management.
LA
Lashon
12 months ago
If the server is using over 93% of its memory, could it be that it's swapping to virtual memory? That sounds familiar.
LI
Lisbeth
12 months ago
I think the Object Calculation Time Limit might be a factor, but it seems more related to memory management issues.
BR
Brendan
1 year ago
I remember something about memory usage affecting performance, but I'm not sure if it's related to the cached results being dropped.
RA
Raul
1 year ago
I've seen issues like this before with QlikView servers. Based on the information provided, my best guess is that the server has started swapping physical RAM to virtual memory, which would explain the performance problems. I'll select that option and move on.
FE
Felice
1 year ago
Okay, this is a tricky one. The high memory usage and working set values point to some kind of performance problem, but I'm not sure which of these options is the correct answer. I'll need to think it through carefully.
MA
Marjory
1 year ago
Hmm, the high memory usage and low/high working set values suggest the server is struggling to manage its resources effectively. I'll need to analyze the options to determine the most likely cause.
SA
Sanjuana
1 year ago
This looks like a memory management issue with the QlikView Server. I'll need to carefully consider the information provided about the memory usage and working set values.
FR
France
1 year ago
Ah, the joys of server performance issues. I bet the IT team is running around like headless chickens right now, trying to figure this out.
NO
Novella
1 year ago
I'm a bit stumped on this one. Maybe the QlikView Server PGO files have been removed? That's my guess, but I could be way off.
WI
William
1 year ago
D) The QlikView Server has begun to drop cached results from memory
CA
Cathrine
1 year ago
C) The QlikView Server swapped physical RAM to virtual memory
CH
Cheryl
1 year ago
A) The QlikView Server PGO files have been removed
ST
Stefany
1 year ago
This is a tricky one, but I'm leaning towards B. The Object Calculation Time Limit has been reached, which could be the culprit here.
DE
Demetra
1 year ago
C) The QlikView Server swapped physical RAM to virtual memory
GL
Glory
1 year ago
B) The Object Calculation Time Limit has been reached
BL
Blair
1 year ago
A) The QlikView Server PGO files have been removed
VA
Valentine
1 year ago
I'm going with D. The server is dropping cached results from memory, which could definitely slow things down for the users.
TH
Theola
1 year ago
We should look into optimizing the memory usage to improve performance.
HA
Hana
1 year ago
That makes sense, it could definitely slow down performance for the users.
LE
Leanna
1 year ago
I think the issue is that the server is dropping cached results from memory.
KR
Kristel
1 year ago
Hmm, I think the answer is C. The server is swapping physical RAM to virtual memory, which can cause performance issues. Makes sense to me.
LE
Leonie
1 year ago
Dropping cached results could also be causing the slow performance.
CA
Candida
1 year ago
D) The QlikView Server has begun to drop cached results from memory
FR
Frank
1 year ago
That could definitely be the issue. Swapping to virtual memory can slow things down.
JA
Janessa
1 year ago
C) The QlikView Server swapped physical RAM to virtual memory
NO
Noah
2 years ago
I believe option D could also be the cause. Dropping cached results from memory can lead to slow performance.
CI
Ciara
2 years ago
I agree with Renato. When the server swaps memory, it slows down the performance.
RE
Renato
2 years ago
I think the performance issue is caused by option C, swapping physical RAM to virtual memory.