Wed, Sep 25, 3:28 PM CDT

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Sep 25 2:58 pm)



Subject: Poser Tip : memory and Hard Drive "virtual memory"


crowbar ( ) posted Fri, 16 January 2004 at 7:17 AM ยท edited Tue, 03 September 2024 at 10:19 PM

I was using poser and getting mighty irritated that with a pc that had 1.5 gig of ram & big harddrive I was getting messages saying insufficient space etc all the time. Then the light switched on and in control panel/ system/advanced I checked how much hard drive space was allocated as virtual memory to the drive that had poser on it. Turns out I was only allocating 300 mb : ( a quick change to the number and no more problem


dontbotherme ( ) posted Fri, 16 January 2004 at 1:19 PM

That extra zero makes a big difference ;-)


Nance ( ) posted Fri, 16 January 2004 at 2:34 PM

It's like a bad horror movie ...you just think it's dead. Don't go in the cellar!


dontbotherme ( ) posted Fri, 16 January 2004 at 2:53 PM

Oh, okay. I'm just going out to the garage. I'll be right back.


JohnRender ( ) posted Fri, 16 January 2004 at 4:01 PM

This still doesn't answer the question on why Poser needs 300M of virtual memory when you've got 1.5G of real, physical memory. You have roughly 5x more real memory available, but adjusting the virtual memory makes a difference??


ynsaen ( ) posted Fri, 16 January 2004 at 4:59 PM

Although tat wasn't the question, here you go: Because it wasn't written to do so, and becuase even if it were, windows would not allow it to do so. Complex operations involved in performing the tasks to which Poser (and most other digital arts applications) are applied are quite RAM intensive at times, and Will be used according tot he most efficient method possible without interfering with other applications. RAM is used first. THe moment RAM is "full", windows, rather than simply telling you "no, you can't do that", shunts chunks of information in RAM to the hard drive in a set location that it is familiar with (and which you can set the size and location of) that is called the "page file" or "swap file". If there is not enough room in BOTH the RAM and the pagefile, then you get the message out of memory. When this happens, the reasonable person will adjust their swapfile up beyond the point of their RAM, so that there is enough space to dump what ever process happens to be running at that time into it (in other words, enough space to store the entire uncompressed file that's already in RAM). Which is what was done. Virtual memory (the pagefile/swapfile) makes a huge difference, as it acts as, literally, extra RAM. If his system had RAM of 8GB, then it's possible he wouldn't have needed much of that swapfile. But since a poser scene can gets quite large (124 jpg tetures, 13 V3's, poser itself, 24 materials, dozens of props) it sorta happens that it will fill ram quite fast.

thou and I, my friend, can, in the most flunkey world, make, each of us, one non-flunkey, one hero, if we like: that will be two heroes to begin with. (Carlyle)


biggert ( ) posted Fri, 16 January 2004 at 5:20 PM

thanks for the info ynsaen.


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.