Forum: Poser - OFFICIAL


Subject: But I Thought Page Faults Were Bad?

nerd opened this issue on Sep 16, 2002 ยท 17 posts


mjtdevries posted Wed, 18 September 2002 at 4:35 AM

No. You cannot allocate memory to a specific program in windows. Windows will just give any program as much memory as it asks for. (Windows will keep a decent amount of memory for filecache and to keep important DLL's and windows code in memory). When you allocate memory in Adobe it only tells Adobe how much memory to ask from Windows. (That why you can limit the amount of memory it asks for to save for other programs, or even exaggerate so that no swapping is required when it needs more) A Page fault basically means nothing more then that Poser asked for a piece of memory that wasn't stored in RAM, but that was stored on the disk in the swapfile. When you see lots of Page faults, (a page is small, so if you need a couple of MB from the swapfile you quickly have lots of page faults) it means that Windows didn't have enough memory available in RAM to supply to Poser. Of course swapping is really slow, so it should be avoided if possible. Two remedies: 1) Buy more RAM. I'd advise to run Performance monitor in the background and measure the amount of memory poser wants. That way you can see how much RAM it asked for and how much you should buy to keep it happy... 2) Try to free up memory by closing programs in the background that use lots of it. BTW those memory cleaning tools you can find on the web DO NOT help for this. (If people want to know why, I'll be happy to explain it, but I don't think that that adds anything to this thread at this moment) Setting a priority only applies to the amount of CPU time a program receives when it has to share it with other programs. It doesn't do anything to memory. By default the foreground application will get a bit higher priority in windows. (Except in server versions)