I don't know if this is a bug, a feature or just me overlooking a change
in default setting, but I have seen that the same scene uses a lot more
memory when rendered with 3.5b4 than with 3.1g. Have anybody else
noticed that, too?

The scene I'm working on currently uses 167MB in 3.1 and 339MB in 3.5. I
have tried a couple of other scenes, and the increase in peak memory use
is between 1.5x and 2x.

Windows NT4 SP6, PIII and Athlon, v. 3.5b4

/Ib

Post a reply to this message

As Thorsten Froehlich advised, I will describe some experiences with memory
usage of different Pov-Ray derivatives.

I took an older maketree scene and put the resultant tree in a while loop
which creates 9 trees. Trunk and twig texture (normal, but none of the
standard textures) was asigned seperately to every cone and sphere
(dotexture = true).

Peak memory usage was 148 MB with v. 3.1g and 579 MB with v. 3.5b4.

When the same texture was asigned to the tree as an entity (dotexture =
false),

peak memory usage was 121 MB with v. 3.1g and 182 MB with v. 3.5b4.

Why is there such a great difference in memory usage wihin 3.1g and 3.5?
Changes in texture management?


memory when rendering the same scene as v. 3.5.

Norbert Kern

Post a reply to this message

I don't know what is the exact answer, but let me throw a wild guess:

  The structs containing object information have grown, ie. they have more
items inside them. Some new features require some extra data in objects and
other similar items.
  This of course means that each object takes more memory and this can be
seen when creating lots of them.

  If this is the reason, the only solution I can think of is to try to look
if the object structs could be optimized for size (eg. use 'union' instead
of 'struct' wherever possible, merge two variables into one if possible, and
so on).

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

In article <3bba3d49@news.povray.org> , Warp <war### [at] tagpovrayorg>  wrote:

>   The structs containing object information have grown, ie. they have more
> items inside them. Some new features require some extra data in objects and
> other similar items.

Not that much, especially compared to MegaPOV.


    thorsten


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

On Wed, 03 Oct 2001 11:47:41 -0400, Thorsten Froehlich wrote:
>In article <3bba3d49@news.povray.org> , Warp <war### [at] tagpovrayorg>  wrote:
>
>>   The structs containing object information have grown, ie. they have more
>> items inside them. Some new features require some extra data in objects and
>> other similar items.
>
>Not that much, especially compared to MegaPOV.

I don't see it turned on in the Windows config.h I have, but is it possible 
that the betas have memory tracking enabled?

-- 
plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip x}rotate
z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red 1rotate 60
*z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb z}text{ttf"arial.ttf"
"RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron Parker

Post a reply to this message

In article <slr### [at] fwicom> , ron### [at] povrayorg (Ron
Parker) wrote:

> I don't see it turned on in the Windows config.h I have, but is it possible
> that the betas have memory tracking enabled?

The Mac one has, but I don't think the Windows one does.  However, while it
could account for the 121 MB vs 182 MB, I am not sure how there can be a 148
MB vs 579 MB difference without either some change in texture assignment or
something (unnecessarily) getting copied for each part.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message