Fri, Nov 22, 12:25 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 21 6:06 am)



Subject: Poser swapping despite free memory available?


Michael314 ( ) posted Sat, 06 October 2012 at 4:58 PM · edited Fri, 22 November 2024 at 7:37 AM

file_487351.png

Hello,

is it possible that Poser Pro 2012 does not use all available memory? For some scenes, Poser suddenly starts high disk activity and CPU usage goes down at the same time. This is usually an indication of swapping. However I have lots of RAM free, as my Windows task manager shows:

 

Is there some Poser setting or Windows setting to allow usign all RAM?

(I'm using Windows 7, 64 Bit and Poser Pro 2012, 64 Bit)

Best regards,

   Michael


Michael314 ( ) posted Sat, 06 October 2012 at 4:59 PM

file_487352.png

mem usage


monkeycloud ( ) posted Sat, 06 October 2012 at 5:03 PM · edited Sat, 06 October 2012 at 5:03 PM

The first thing I now check, if I notice this issue, is whether there are any image_map nodes in my shaders that have texture filtering set to "none".

As far as I understand it, this prevents the image textures being cached in memory and means more (single threaded) disk IO...


wimvdb ( ) posted Sat, 06 October 2012 at 5:08 PM

As you can see in the last picture - available free physical RAM is 1 MB. This means that Windows has to free up RAM which other programs have allocated. (RAM available). This is normal Windows behaviour.

PP2012 does use all of the memory when it needs it. I have done scenes which use 24GB and does so without swapping (I have 32GB in my system)

 


ashley9803 ( ) posted Sun, 07 October 2012 at 2:51 AM

It does seem that Poser (and any other programs you have running) is eating up your hard mem.

Bear in mind virtual memory is always being used, even when the memory that is required by all running processes does not exceed the volume of RAM that is installed on your system.

What I'd like to know is why Firefox consumes up to half a gig of memory for a damn web browser... but that's another issue.


aRtBee ( ) posted Sun, 07 October 2012 at 2:56 PM

It's not Poser, it's your system eating the memory, as it says that it has created over 800.000 handles. The usual remedy is to start rendering as a separate process (well, it is Poser after all, when the render is finished the handle mem is not freed up). Or you can restart Poser after every so many renders, but that's less convenient.

We had a thread on this some time ago.

- - - - - 

Usually I'm wrong. But to be effective and efficient, I don't need to be correct or accurate.

visit www.aRtBeeWeb.nl (works) or Missing Manuals (tutorials & reviews) - both need an update though


Michael314 ( ) posted Thu, 11 October 2012 at 1:53 PM

Hi,

thanks a lot!  Yes, it looks like that there is in fact only very little RAM free.   This could be due to a Windows bug, I found some threads concerning issues with NUMA CPUs (I wonder if I have one?), for example here: http://support.microsoft.com/kb/2155311/en-us

Rendering in a separate process (for example using Queue manager) seems to be a good solution, which will have the additional benefit that I can further tweak the scene while the render is in progress...

Re the browser memory consumption: I usually have loooots of tabs open. Once when I closed a browser but took notes about the pages I counted more than 200... 

 

Best regards,

   Michael 


aRtBee ( ) posted Thu, 11 October 2012 at 2:45 PM

Render as a seperate process is an option in the preferences, but you need Queuemanager indeed to continue working in Poser while rendering.

- - - - - 

Usually I'm wrong. But to be effective and efficient, I don't need to be correct or accurate.

visit www.aRtBeeWeb.nl (works) or Missing Manuals (tutorials & reviews) - both need an update though


wimvdb ( ) posted Thu, 11 October 2012 at 2:45 PM · edited Thu, 11 October 2012 at 2:46 PM

To render in a separate process, you only need to tick it on in the General Preferences. You can also render in background while continue to work on the scene.

No need to run Queue Manager (although that has its advantages).

Edit: crossposted with ArtBee

 


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.