Out of virtual and/or logical memory, allocating 0.5 MB

[#1]

I'm trying to open a QlikView doc from my workstation but receiving an error "

Out of virtual and/or logical memory, allocating 0.5 MB". I have Qlikview 8.5, 32-bit version with 3 GB RAM and 30 GB virtual memory. The QVW is 609 MB.

I can open the same document when I'm logged on to the server which has Qlikview 8.5 64-bit version with 32 GB RAM.

I want to use my QlikView Professional license on my workstation to do development rather than having to log on to the server to do development.

Why does the error message say it's only allocating 0.5 MB when I have virtual memory set to 30 GB?

Is it possible to work with a QVW this big on my workstation, or am I going to have to continue using the 64-bit version while logged onto the server?

[biester]

Hi,

I'm surely not a QVMMG (= "QlikView Memory Management Guru" 😉 and perhaos I'm totally wrong, but I can say from experience that a QVW with 609 MB is surely a LOT of data. Actually with 32 bit a process can only use 2 GB of memory (you can have as much virtual memory as you like, the 2 GB limit is not affected by that). In the boot.ini you can tune to max 3 GB, but that's it then. If a QVW thus big not running un 32bit IS running on 64 bit I'm pretty sure it's the 2 GB limit. Can't tell you details for the 0.5 MB message - but I'm afraid that without optimization or data reduction (if possible) you won't get it running on 32bit.

Rgds,
Joachim

[johnw]

Any time I see that message, it pretty much means "QlikView is now crashing". As Joachim indicates, you're limited to 2 GB of addressible space per application. So even if you could use the 30 GB of virtual memory, which you can't, you really wouldn't want to. The performance is based on QlikView manipulating ALL of your data in RAM. If you have to swap any of that to disk, it's going to slow to a crawl.

I'm afraid you're just going to have a hard time doing development on your workstation. I have the same problem where I work - I do most of my development on a 32-bit machine, but I have several applications that are simply too large for that. For those, I log in remotely to a 64-bit workstation, and use 64-bit QlikView. It is inconvenient but workable.

Unless you've already done a lot of tuning, it's quite possible that your QVW is using a lot more memory than it truly needs. For instance, sometimes people do a LOAD * from sources, rather than just pulling in the fields they need. Not only does that use a lot of unnecessary memory, but it also makes it so that anyone could add a field to the source, which could then cause a new link which could break your application. You may have some synthetic keys or other keys that could be replaced with an autonumber. You may have an occasional text value in a field that could otherwise be efficiently stored as a numeric. You may need to join tables together, or split tables apart. There are lots of possibilities.

QlikView can also export .mem files that you can then load in and analyze to see where the memory is being used. That is sometimes useful.

[#4]

would upgrading to win 7 64bit from win 7 32 bit then upgrade to qview 64 bit fix issue?

[Oleg_Troyansky]

Yes, pretty sure it will - if your document opens just fine on the Server, then the document is OK. 64-bit Windows, with a 64-bit QlikView Client, and with enough RAM (not virtual!!! actual RAM - perhaps 8 GB would work?), you should be able to work with the document locally...

If you can open the document on the server, check how much RAM your job is taking, and ensure that you have at least that amount, and then some...

cheers,

[johnw]

If you go 64-bit all the way around, you're not limited to 2GB of addressible space. But you do "need" to run entirely in RAM, so you're only getting an extra gigabyte since you have 3GB. That may or may not be enough, and you should probably also upgrade your RAM. But I'd only do that AFTER tuning the application. Better a cheap fix that helps every computer the application is on rather than an expensive fix that only helps your computer. Ultimately, though, if the application is simply big, you'll probably need to upgrade to 64-bit like you said.

[#7]

Thanks for the reply. Since the original post, the developer worstations are now 64-bit with 16 GB of RAM. Works fine and now don't need to log onto the server to do development with this large app.

[#8]

I get the "Out of virtual and/or logical memory message, all.."  and I am on 64bit with 16GB of RAM.  My machine only appears to use about 6GB when I get the error.    Any ideas ?

[raghavsurya]

Hi,

Check out for synthetic keys and eliminate them by combining tables/concatenating them, alternatively check for any loosely coupled linkages between tables. 

Regards,

Raghav

[#10]

No synthetic keys or loose coupling,  just lots of data, doc runs fine on a server.  My issues seems to be Qlikview is not using all the available memeory on my PC ?