Discussion Board for collaboration on QlikView Scripting.
I have QVDs and some reports that are written primarily in SQL script. I notice that our PC manually reloads faster that our QV server in almost all cases. A job that takes 2 hours on the server running alone, compare to 20 minutes on this PC running unrestricted.
The specs are as follows:
BFPC: Intel Core i7 2.93 Ghz 8GB Ram
QV SERVER: 8x Intel Xeon(s) 2.66 Ghz 4GB (32 total) Ram
With 8 of these running on our QV server, we cannot understand why the server is not able to run these jobs faster if not match the speed of a local PC reload. I have attached the log of both runs and though it takes the server longer in all parts of the job, the server takes much longer in joins by the looks of it. I know others have had this issue, but I don't see any solutions out there from the community or QV techs.
Let me guess, your run a virtual server and your 8x Intel Xeon is a fact one quad processor with hyperthreading activated. Am I right?
We have another person that is currently in charge of our settings for our server, I schedule, create, and run the different QVDs and reports here. Where would we go to find these settings so I can get back to you 2 on your questions and suggestions? I will work with the guy in charge to investigate.
I note in the server logifle that you have EnableParallelReload disabled. Is that intentional? Did you turn that off at the direction of QT support?
Not that I know, I see now that that is a difference between both runs as well. Could you ellaborate for me on your knowledge/experience with this setting? Is this something that could have an effect on our server reloads?
I believe the setting allows the reload task to distribute work across multiple cores. If you watch Windows Task Manager on your desktop during the JOIN, you'll likely see more than one CPU busy. On your server with EnableParallelReload disabled, I expect you'll see only one CPU being used.
There was a bug back in V10 that required some customers to disable it, but that bug has long been fixed.
I'm not sure where in he config for V11 server thiis is set. Check with support to find out where the setting is.