Open in Server vs Accesspoint RAM

[#1]

Hi all,

I am wanting to find out whether or not more RAM is used when opening Qlikview via the client (Desktop) using 'Open in Server', as opposed to opening Qlikview via the Accesspoint Portal?

Thanks

[#2]

Open in Server will consume more your System (Laptop/Desktop) RAM and server RAM does not effect in this case.

If you oped the Qlikview dashboard through Access Point URL, both server and your system RAM were consumes because its web application.

[#3]

Hi Dathu,

Thanks for your quick response.

So does this mean that it would consume more server memory, by opening up via the 'Open in Server' option?

Thanks

[#4]

There is no server RAM consumes while "Open is Sever" option you choose.

But for this, you need a NAMED CAL on Qlikview desktop client to lease the licence from server.

[#5]

Hi Dathu,

Thanks.

Yes, we have a number of named CALs for each client to lease a license.

I'm trying to find out RAM consumption with relation to performance and how it impacts the server.

Cheers

[sureshbaabu]

Hello,

Hope the following helps.

1)QVD Size + Report Size =  Application Size (.QVW file) - your report

2)When accessed through Access point: (Application Size * 4 ) stores on RAM of Server (This is allocated for the report on server)

3)10 % application size is assigned to an individual users for a report. (Keep adding 10% as the user keeps increasing)

Thanks

[Peter_Cammaert · Accepted solution]

That's not entirely true.

Open in server... is exactly the same as opening a document in the AccessPoint. Your QV Desktop becomes a QVS client and does the same thing as the QlikView plugin for IE, but now in a nice desktop environment. And this works equally well with a Document CAL.

If you use Open in server to open an AccessPoint document, you can test memory consumption differences by turning WebView on (to test AJAX client behavior) or OFF (to get plugin behavior). Although it won't be exactly the same as testing it with individual clients.

Peter