senyac opened this issue on Aug 14, 2009 · 15 posts
senyac posted Fri, 14 August 2009 at 9:52 AM
Hi I thought I would check Poser 6 and 7 Vs Poser 8 memory usage ,
My system is a Intel(R) Core(TM)2 Duo CPU
E4800 @ 3.00GHz
4GB ram with the 33b switch enabled
Win XP pro .
I have 80 gb of runtimes and they are all linked to all versions of poser
Running Poser 6 with an empty scene uses 96,304kb of memory ,
Running Poser 7 with an empty scene uses 120,136kb of memory ,
Now with Poser 8 I have the script to turn ON of OFF the library
and so
Poser 8 with an empty scene with the library turned OFF uses 129,352kb of memory
BUT
Poser 8 with an empty scene with the library turned ON uses 231,884kb of memory
So its seams this New library system while its easier to use but with a down side of using almost double the memory of poser 7 and double the memory in poser 8 than if the library is turned off :(
So now I am not sure if I like his new library or not lol
Gareee posted Fri, 14 August 2009 at 10:05 AM
It makes sense if the li9brary is cataloging and using additional items, that its going to require more memory.
Yer talking the difference in maybe one texture file, not even worth the bother or consideration.
Way too many people take way too many things way too seriously.
senyac posted Fri, 14 August 2009 at 10:14 AM
well I am having alot of out of memory errors with P8 which i dont have with P7 and so i am just trying to see what is different between poser 7 and 8 :)
Funny thing is some of these P8 out of memory errors occur after P8 has finished a render lol
SO it had enough memory to complete the render but not enough memory to return to the preview window? lol
Must be a memory leak or just bugs that need exterminating .
I am looking forward to the SR1 :)
Gareee posted Fri, 14 August 2009 at 10:23 AM
Well everyone is reporting better memory usage in P8 vs older versions.
How much ram do you have, and what OS?
Way too many people take way too many things way too seriously.
AnAardvark posted Fri, 14 August 2009 at 11:17 AM
Quote - well I am having alot of out of memory errors with P8 which i dont have with P7 and so i am just trying to see what is different between poser 7 and 8 :)
Funny thing is some of these P8 out of memory errors occur after P8 has finished a render lol
SO it had enough memory to complete the render but not enough memory to return to the preview window? lol
Must be a memory leak or just bugs that need exterminating .I am looking forward to the SR1 :)
Are you using "Texture Shaded" for your display? Poser 8 is a lot more aggressive about using shader trees (it uses transparencies, for one thing), and these texture maps have to go through main memory before going to the video card.
senyac posted Fri, 14 August 2009 at 11:39 AM
@ Gareee ,
I have 4gbs of ram on Win XP pro with the 3gb switch enabled ,
@AnAardvark ,
Yes I am using "texture shaded" for my display just like I do with Poser 7 ,
In Poser 8 I have tried all the different setting EG:
Open GL Hardware/software ,enable hardware shading On and Off
Transparency Display - actual , limit to 50% and enhance multilayer tranparency On and Off ect
and changing these setting seams to have no effect on whether or not I get the out of memory errors :(
Although Turning enhance multilayer transparency doe slow down the UI a bit
BTW I have a ATI RAdeon HD 4850 with 512mbs ram
I have read in other threads about some other people have the same out of memory errors .
Gareee posted Fri, 14 August 2009 at 11:59 AM
Well, all I can tell you is opengl is only handled by your video card, not by your ram. If you switch to sreed, THEN its handled by your main onboard ram.
I noticed the video memory increase when I upgraded to my last videocard, so the memory setting for poser's preview IS addressing video card ram use.
The only posts here I've seen about poser 8, is how much better it manages ram use.. this is the first I've seen anywhere to the contrary.
Course you are also using an old OS that doesn't handle large amounts of ram properly as well... and if you upgraded, you'd find Vista pre gobbles even more of your ram.
Memory is cheap though.. all my systems here for 8 gb now. I think I bought 4 gig of ram for under $50 the last time I purchased it.
Way too many people take way too many things way too seriously.
senyac posted Fri, 14 August 2009 at 12:18 PM
@ Gareee
see :
http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2779066
acouple people in that thread are having OOM errors too ,
As for upgrading I think I will wait for Windows 7 to be released .
Gareee posted Fri, 14 August 2009 at 12:27 PM
Why not download and install the windows 7 beta now then? Seems silly to cripple your use now for no real good reason.
Way too many people take way too many things way too seriously.
raven posted Fri, 14 August 2009 at 1:03 PM
P7 used transparency maps in the preview just like P8. Here's a screen grab from the preview window in P7 showing the display using trans maps.
senyac posted Sat, 15 August 2009 at 2:42 AM
More p7 vs P8 tests today :)
Same scene with same render settings ,
Poser 7 with bucket size of 64 renders the scene without any problems using 60% of memory ,
Poser 8 with bucket size of 64 and the render fails about 75% complete because memory has reached 100% :(
Ok Then with Poser 8 i use Seperate proccess and a bucket size of 32 (should use less memory)
and again render fails at about 75% complete because memory has reached 100% and get an error saying FFrender.exe has had a problem and needs to close :(
Sure I can get Poser8 to render a simple scene without a problem but a more complex scene Poser 7 can handle it BUT Poser 8 can not :(
Its dose appear Poser 8 has some memory issues/leaks
I hope these are fixed in SR1
TrekkieGrrrl posted Sat, 15 August 2009 at 3:12 AM
The OOM issue MAY be due to the TEMP path being faulty in Poser 8. It's a known bug, and Poser doesn't clean up Temp files as it should. They accumulate on the harddisk, and if the temp path is on a drive with not much free space, that may clog up everything. Did you change the temp path or left it at the default location? In both cases, try deleting all the temp files (I bet you it's HUGE!) and see if that helps.
FREEBIES! | My Gallery | My Store | My FB | Tumblr |
You just can't put the words "Poserites" and "happy" in the same sentence - didn't you know that? LaurieA
Using Poser since 2002. Currently at Version 11.1 - Win 10.
senyac posted Sat, 15 August 2009 at 3:21 AM
I left the Temp as the default location and I just checked it and its empty ,
No problem with drive space ect Drive C has 90gb freeand Drive D has 600gb free drive E has 400gbs free :)
I think its more of a Poser 8 bug seeing I have no issues with Poser 7 .
roll on SR1! lol
JoEtzold posted Sat, 15 August 2009 at 1:10 PM
Don't forget the Flash plugin to be used for the new library.
So with library set to OFF via the script = no Flash loaded, memory free but with active library flash is wasting some memory. That should make the difference.
Kaylic posted Tue, 25 August 2009 at 10:58 AM
I'm having this same problem. I will get "out of memory" sometimes with only a single, clothed V4 and no scenery, yet i can have that same figure along with a complex scene with the same render settings and it will render fine in P7. Even more odd is that if I look in the windows task manager I still have quite a bit of memory available. In p7 there are times where it is using close to a gb of ram during a render and it will finish, yet I'll get "out of memory" in p8 at 400-500mb ram usage.
I've also had the same thing happen where it will give that message after the render completes, while it is going back to the preview state. My drivers are up to date so I'm just stumped. It does seem to be a bug of some kind. I guess it's time to wait for the next update and hope it's fixed.