ingo wrote:
>When parsing big files and memory use goes upto 2Gb a window pops up that
>says that I've ran out of memory. When I close the window and then POV-
>Ray, my machine resets. I don't like the resetting part.

Ingo,

I might be able to render it for you on a machine here that has lot's of
memory. Let me know if you need it.


Thomas

Post a reply to this message

in news:3d734467$1@news.povray.org Gilles Tran wrote:

> Just wondering, what caused this huge memory requirement in your scene ?
> 

In this case it was usual badly constructed mesh generation macro (forgot 
to put a decimal point in somewhere). But generaly it's the use of 
severeal big mesh that need to be copied to give them different textures, 
radiosity, photons and big 3D-data sets.

Ingo

Post a reply to this message

in news:3d734c0c@news.povray.org Thorsten Froehlich wrote:

> The only other options would be the servers Sun or the many
> other companies sell, but the price tag is out of Ingo's reach, I
> suspect 
> 

The Blade 2000 ones look nice, but I'd rather spend that money on a pair 
of GOTO SG-38WNSS woofers. :)

Anyway, what are the advantages of 64 bit systems? Only the amount of 
adressable memory or will they also render faster?

Ingo

Post a reply to this message

In article <Xns### [at] povrayorg> , ingo <ing### [at] homenl>  
wrote:

> Anyway, what are the advantages of 64 bit systems? Only the amount of
> adressable memory or will they also render faster?

Only the addressable memory.  POV-Ray needs no the other features.  As for
the render speed, it depends on the processor and subsystems, not at all on
the address space (well, it does atiny little bit, but to such a technically
complicated extend that i will leave it out).

    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

in news:web.3d735005f29d4e58bbe30ae0@news.povray.org Thomas wrote:

> I might be able to render it for you on a machine here that has lot's of
> memory. Let me know if you need it.
> 

Thanks for the offer Thomas, 
I won't need it right now, but in the future, who knows.

Ingo

Post a reply to this message

ingo <ing### [at] homenl> wrote:
> Anyway, what are the advantages of 64 bit systems?

  64-bit memory access. 64-bit file access (ie. you can have up to at least
2^63 bytes big files without needing to modify your programs). 64-bit long
type.
  And the render times will not be any faster (unless povray needs HUGE amounts
of memory). They will probably be some percents slower (because caches fill up
faster with 64-bit code).

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

Post a reply to this message

ingo <ing### [at] homenl> wrote in news:Xns### [at] povrayorg

> Probably more a windows problem than a POV-Ray problem, but I thought
> I'd report it here, just in case.
> Athlon 1800+, 1.5 Gb, Win2000, POV-Ray 3.5

maybe useing Linux with large swap partition will help ?


-- 
#macro g(U,V)(.4*abs(sin(9*sqrt(pow(x-U,2)+pow(y-V,2))))*pow(1-min(1,(sqrt(
pow(x-U,2)+pow(y-V,2))*.3)),2)+.9)#end#macro p(c)#if(c>1)#local l=mod(c,100
);g(2*div(l,10)-8,2*mod(l,10)-8)*p(div(c,100))#else 1#end#end light_source{
y 2}sphere{z*20 9pigment{function{p(26252423)*p(36455644)*p(66656463)}}}//M

Post a reply to this message

On Mon, 02 Sep 2002 07:31:25 -0400, Thorsten Froehlich quoth:

> In article <3D7346FA.729D5BD1@gmx.de> , Christoph Hormann
> <chr### [at] gmxde>  wrote:
> 
>> Neat, but the data sheet says it only supports up to 2 GB memory on
>> board and what's 64 bit address space worth with only 2 GB memory.
> 
> I know, but it is the cheapest available 64 bit workstation I know
> about. And applications will be able to use all the virtual memory the
> harddisks can provide.  The only other options would be the servers Sun
> or the many other companies sell, but the price tag is out of Ingo's
> reach, I suspect ;-)

He could get an SGI Octane2 workstation -- it has a 64bit processor and
can support up to 8 GB of physical memory.  Unfortunately, the system is
designed for triangle-based OpenGL graphics, so the processor isn't too
impressive: the fastest CPU available for it is a 600MHz one.  They run
about $15,000 to $30,000.

-- 
Mark

Post a reply to this message

I've read the discussing so far, and I really ask myself why PovRay crashes
at such a memory usage. Surely this is not a standard test-case, but still,
I don't think it should crash. There are databases, CAD and other apps
running on W2K that do use up to 2 GB of memory, and I never heared they
crashed when tried to shut down.
My guess is some memory-allocation-fails case is not handled properly. I
don't have any idea how this could lead to a reset, either a bug in POV, or
in W2K (or, maybe most probable in both)

I've rendered a scene that hits my memory limit (sad to say, a 256 MB limit
is reached quite quick...). POV did neither crash nor reset. In fact after
the W2K message box "...too little virtual memory..." the scene rendered
fine...

Niki

"ingo" <ing### [at] homenl> schrieb im Newsbeitrag
news:Xns### [at] povrayorg...
> When parsing big files and memory use goes upto 2Gb a window pops up that
> says that I've ran out of memory. When I close the window and then POV-
> Ray, my machine resets. I don't like the resetting part.
>
> Probably more a windows problem than a POV-Ray problem, but I thought I'd
> report it here, just in case.
>
> Athlon 1800+, 1.5 Gb, Win2000, POV-Ray 3.5
>
>
> Ingo

Post a reply to this message

In article <3d74861b@news.povray.org> , "Niki Estner" 
<nik### [at] freenetde> wrote:

> My guess is some memory-allocation-fails case is not handled properly.

Bad luck with this guess here.  All memory allocations are handled with the
same abstraction layer for memory allocations which temselves check every
access.  So it cannot just fail somewhere.  It is a Windows problem.  Might
be i.e. some system function that does not like running out of memory...

    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