I'm experiencing high RAM and CPU usage while using the expression editor in Qlikview x64 version 12.10.020200 SR4.
Any change in the expression leads to 100% single thread CPU usage + 50GB RAM usage for a couple minutes.
Is there any reason for Qlikview to compute the expression while the user makes the changes?
After a while the RAM usage drops to normal levels.
Is thata BUG? Is there anything wrong with my expression?
The SQL query would be as simple as:
WHERE B > 2*C
GROUP BY D
Table would be like:
A B C D
1 10 30 A
2 20 25 B
Can't Qlikview do a simple select efficiently?
This implies that QlikView somehow tries to precalculate the expression search you are using. Might be a bug.
Should be easy to test if the same happens in 11.20 if I only had a simple table with a few million lines of data...
Same issue reported here: 40 Mb file exceeds 3 Gigs on Task Manager
It seems Qlikview uses some really crappy algorithm for aggregation...
Time to go back to school guys, relational database technology is almost 50 years old!
Interesting. I had not noticed this before. But when the modifier value contains a leading "=" (Advanced Search), QV seems to calculate the expression on the fly as you type. This can be annoying.
I tested on V11.20SR15 (and earlier QV11) and V10Sr6 and the behavior is there as well. A workaround is to type the leading "=" after you have completed your editing.
I've attached an example that demonstrates the issue.
Thanks for the feedback, Rob!
I'm going to avoid the memory use problem by moving the calculation of the ration between the two columns to the load script and make the set expression using a constant instead of making reference to two columns in the same row.
But I really don't get why Qlikview needs so much memory in order to do this kind of aggregation, it's many times greater than the original data uses. Is there a better way to do it?
Do you think there is room for improvement in the way Qlikview is implementing this kind of set operation?