Maxwell Render | Official public forum

i am wondering about how the merging process of cooparative files is done in V2 network render.

having a heavy multilight file.. (2gb mxi) when i stop the job, the mxi get transfered and then the ram of the computer running the manager goes wild.. hitting almost 5GB!!

i also have a little batch command getting the mxi from the nodes "by hand" to merge manually.. when merging that way with maxwell.exe ram usage is way lower @something like 200mb....

is it not odd why it would need so much ram..? i can't have any other ram hungry application running in the background and the manager has to run on a potent x64 machine. I used to run mx sever on an older 32bit file server, which is no optinon anymore with v2... it is more blocking one of my workstations now.

I can see the benefits of the new system in v2.. but it woulde be great if you could add some "manual" coop mode, which collects mxi to a given folder and allows to terminate a job completly without starting to merge mxi, becasue atm it leaves the whole farm useless for a long time, and often merging fails anyway....

regards,

Daniel

BUMP.

this is form a machine that is NOT rendering anything... just running manager/monitor.. also the ram is not purged after job the job completes.

does it have to be this way?? it is very inconvinient.

If you reset the nodes from the monitor, will it purge the RAM? I agree I don't like how it holds it after the job is done.

If you reset the nodes from the monitor, will it purge the RAM?

hi Bubba!

no it does not.. and it's Ram usage increases everytime i add another job.. or at least it increases and then went back to 4.8GB

i assume that the manager tries to hold all data in ram.. so the scene file (when distrubuting to the nodes) and later the mxi form the nodes, to merge faster (not dependant on HD speed)....the problem with this is just that i need to buy an extra computer with at least 8 GB ram just for running netrender...

this is what i had just now: