#Memory
3 messages in this thread
I was wondering if there is some sort of memory management problem in release
2.0 – which is what I'm using. It seems that once it fills memory and starts
paging to the HD it never releases the memory again unless you quit and restart
it. Even doing a reset doesn't let the memory go. Is this something fixed in
the updates or hasn't it been dealt with – or am I missing something. I have a
486/66 (gateway 2000) with 20Mb of ram and some of my renderings (not many) are
paging to the HD. Also, when I first load a large mesh everything is ok until I
render it – then once memory fills up it doesn't give it back even when it is
done rendering. So I save – exit – and come back and work with the mesh some
more. Well, any insight would be appreciated. Thanks Dave Mennenoh 71561,2343
David, please read the note on page 70 of the 3DSr2 Installation and
Performance Guide. It discusses how Phar Lap 2.x doesn't allow the swap file
to be "zero'd" out without exiting the program and restarting.
Now that we're working with Phar Lap 4.x for r3, we're hoping to make tthis a
bit more elegant. We'll see…
– G
Thanks for the info. Hopefully ver 4.x will take care of it. One more quick
question on memory while I'm at it. In the text file that describes how to
compute how much mem will be needed at rendering time, I don't quite understand
the mapping one. It says to multiply horiz x vert x 3 to get the mem
requirements for that particular map. Do I need to add this in for every
instance of that map? Say I use wood-teak on 5 different objects, do I need to
multiply the horiz x vert x 3 x 5 or do I need to do it just once? I think it
is every instance but I would like to be sure since after calculating it out I
need 19.6 MB (I have 20 MB) but I have a 12MB swap file whan it is done.
Thanks again Dave