[Boris Ulzibat]

I am running Maxwell on Macpro, which had 3GB of ram. It broke down, so i had to repair it and it was a good chance to upgrade it with 1 more GB of RAM.
I have XP32 and Mac OS X on it, and XP sees only 2 GB, while Mac OSX sees all 4 of them. The top resolution jumped from 3500*3500 to 5000*5000.
The thing is, the 64 bit version of maxwell is talked about for a long time, but for me it seems like Mac version of maxwell already has the 64 bit memory allocation functionality (at least).

So, can anyone tell me, if the 64 bit version of maxwell for windows is still needed to take advantage of more RAM on Win 64bit. Or it is not the whole case and 64 bit Win can give Maxwell a lot of RAM right now?

I am a bit of a noob in these matters, sorry...

[aitraaz]

Yup, the 64bit release of maxwell on winxp64 will be able to access more ram than the current 32 bit version.

And nope, until maxwell win 64bit is released, running it as 32bit on xp64 it have still have the same ram access limitations. (give or take a little)

[deadalvs]

mac os has a very efficient memory handling system since mac os is built on a unix kernel. but the max of it is around 3.5 [ - 3.9 GB] per application, question of optimization of the software of course. i thought one user here did a test with a small program and came to 3.9 GB !

but maxwell on osX is not yet 64 bit-optimized...

* * *

by changing from osX to win32, i felt a speed increase of 15% ! i can not say anything from 32 to 64 since i have only a new computer running 64

[Boris Ulzibat]

Yep. i figured out that 4 GB per app is a current naximum for OS X.
Though in terms of resolution 4 Gb is much better than 2 I can render hirez now
Seems like waiting for a true 64 bit Maxwell and a true 64 bit Leopard is worthy!

[deadalvs]

the question, if a native 64 bit version for osX is in the pipeline or not, is left unanswered ...

[Boris Ulzibat]

the question, if a native 64 bit version for osX is in the pipeline or not, is left unanswered ...

Let's hope for the best, in fact it is the only choice here

[Maximus3D]

This is difficult to answer i know but wonder if XP64 will give you any benefits running a 64bit Maxwell with a system that only got 2GB ram. Anyone wanna speculate and guess ? ..or even better, if NL knows.

/ Max

[Boris Ulzibat]

Nope, my system has 4 GB, but XP 32 bit sees only 2 GB.
I am planning to use Mac version if possible though


I hate Windows...

[deadalvs]

xp32 --> xp64:
the only possible advantage might be a little to negligable speed gain.

[aitraaz]

the question, if a native 64 bit version for osX is in the pipeline or not, is left unanswered ...

Well, of course it is. But it ain't gonna be happening before any Leopard release

Nope, my system has 4 GB, but XP 32 bit sees only 2 GB.

Well, with the 3GB switch, your xp32 will see 3gb, better than nothing - why not upgrade to xp64? Maxwell will render at (slighty) higher resolutions, in any case, its well worth the upgrade....

[Boris Ulzibat]

I don't know, really... I work in OS X mostly anyway...
But yes, i think the upgrade 32 => 64 is a good thing to do!

[Fernando Tella]

I'm using maxwell with XP64 and I've seen mxcl use ~3.4GB of RAM when making the 14million triangles test; the test was launched from 3dsmax plugin. I think studio cannot use more than 2GB though.

[Tim Ellis]

I'm using maxwell with XP64 and I've seen mxcl use ~3.4GB of RAM when making the 14million triangles test; the test was launched from 3dsmax plugin. I think studio cannot use more than 2GB though.

heh.

My maximum limit of memory for MXCL from the command line, was for a 2kx1.5k multilight, which peaked at 4.7GB for 4GB of ram. Over 6.25million verts.

Studio will peak at memory limit, usually for me at about 3.8GB and then crash. Rendering from the command line with no other processes running will allow +4GB memory usage, on x64bit XP pro.

I will be going up to 16GB of ram, but until then I'm not sure of an x32 Maxwell memory ceiling on an x64 system, if there is one.

Tim.

[Fernando Tella]

heh.

My maximum limit of memory for MXCL from the command line, was for a 2kx1.5k multilight, which peaked at 4.7GB for 4GB of ram. Over 6.25million verts.

More memory than you've got! Maybe 3.7?

Studio will peak at memory limit, usually for me at about 3.8GB and then crash. Rendering from the command line with no other processes running will allow +4GB memory usage, on x64bit XP pro.

Great! I don't use studio much and I thought I had suffered some crashes due to memory, but I was not actually checking the amount of memory. It's great I'm wrong.

[Tim Ellis]

heh.

My maximum limit of memory for MXCL from the command line, was for a 2kx1.5k multilight, which peaked at 4.7GB for 4GB of ram. Over 6.25million verts.

More memory than you've got! Maybe 3.7?

Nope task manager deffinitley stated 4.7GB.

I was sweating it, because it was a client render which really didn't need to crash.



Tim.