Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Emmanuelle__Bustos
Partner - Specialist
Partner - Specialist

Allow Document auto load

Hello everybody

I´ve got a question does anybody know exactly how the "Allow Document auto load" option in the Qlikview Server--> Performance section of the Qlikview Webserver works???

I´ve been testing with my server but i can´t find a difference if i checked the box of this option or don´t.

Does anybody use it or knos how to make a test and corroborate??

I´ll appreciate your help

1 Solution

Accepted Solutions
Anonymous
Not applicable

Hey Emmanuelle,

That's correct. The auto load allows you to load documents into RAM when the QVS service starts. Not connected to the reload, just for being able to serve up documents faster if you have files that you know are being used a lot in the organization.

View solution in original post

6 Replies
StefanBackstrand
Partner - Specialist
Partner - Specialist

The autoload option is actually the same as what's called preload, and this setting in the QVS settings means that the sever allows that documents gets preloaded to memory when the server starts and without having a user to trigger the document to load from disk to memory in QVS. The granular preload itself is controlled via each document under user documents (and in tasks, if publisher) and on each document. This is further described in the server reference manual.

Emmanuelle__Bustos
Partner - Specialist
Partner - Specialist
Author

Hello Stefan

Let me see if i understood, so you mean that if the box is checked the access to the documents are faster because they are "loaded" into memory When qlikview Server starts, right?

And so this option has nothing to do regarding with the Reload Action right?

Sorry that i'm confused because in the reference manual only comes this quote: "Check this box to enable automated document loading and unloading"

Anonymous
Not applicable

Hey Emmanuelle,

That's correct. The auto load allows you to load documents into RAM when the QVS service starts. Not connected to the reload, just for being able to serve up documents faster if you have files that you know are being used a lot in the organization.

Emmanuelle__Bustos
Partner - Specialist
Partner - Specialist
Author

Thanks both of you Stefan and Johannes

sudhanshu123
Partner - Contributor III
Partner - Contributor III

So is it like this. If we have preload option not checked under document tab for one app and autoload option checked under system tab.Then does this mean application will come in memory because of autoload is checked or as preload is not checked so autoload will not bring that application in memory. Kindly help with this. Thanks 
Brett_Bleess
Former Employee
Former Employee

Just wanted to add Help links here that should help any future posters:

QMC Help regarding QVS Performance tab settings:

http://help.qlik.com/en-US/qlikview/November2018/Subsystems/QMC/Content/QV_QMC/QMC_System_Setup_Qlik...

QMC Documents\Source Documents Preload:

http://help.qlik.com/en-US/qlikview/November2018/Subsystems/QMC/Content/QV_QMC/QMC_Documents_SourceD...

QMC Documents\User Documents Preload:

http://help.qlik.com/en-US/qlikview/November2018/Subsystems/QMC/Content/QV_QMC/QMC_Documents_UserDoc...

The last two are basically the same, just a matter of whether you are applying the setting to the Source doc such that on every distribution we push the settings to the User Doc, or the latter where you set on the User Doc directly, but if you do not set things in the Source Doc side and do a QVS distribution, that will overwrite your User Doc setting, just FYI! 🙂

Regards,
Brett

To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.