Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
paulyeo11
Master
Master

my qv when reload it alway stop at master calendar for 1 min

Hi All,

my use my not book yoga 13 to reload my qv doc , it alway stop at master calendar for 1 min. it is normal ?

stop.JPG

11 Replies
paulyeo11
Master
Master
Author

Hi Sir

i just check load with sample data , my reload time = 3:32 min , after remove cal field , the reload time 3:12 min.

conclusion is 10% reduce in reload time.

look like improve only little bit.

stevelord
Specialist
Specialist

Hi, I have scripts that take a few moments to load because they use calculated fields to transform a few million lines of columnar data.  I see you mentioning 'sleep' in your posts.  I notice then when I work with data files on my desktop everything moves faster and loads in a minute or 90 seconds, but if I work with copies of the same files on the network drive (RAID servers scanning everything that moves) it can go a few minutes and show (Not Responding) even though QlikView is still processing the data.

Solution may be to make copies of the needed data tables on your own hard drive to use while developing the script.  If you get efficient enough to run pretty fast while referencing only copes of the files on your desktop, you can probably attribute the slower load times to the hardware used by the networking infrastructure.

Our laptops have 8GB of RAM and have encrypted harddrives but not so many things happening at once, so we can actually run scripts on our laptops that the servers have trouble with- discussion happening about upgrading network infrastructure.   Discussion about whether to upgrade to 16 GB laptops but QV objects seem to have their own internal memory limits independant of our computer's RAM.  Also close/open files if you notice things slow down after you made many changes- things will speed up again (possibly because some buffer or clipboard that was lugging around file change information cleared itself).