Warp(ed)?
5 messages in this thread
>> …can run multiple copies of Studio at once
>> (slave render in the background and work on
>> another copy in the forground).
>> Plus many other feature like 32 bit capability,
>> dual processor support, multi-tasing,…
Ok, this is mostly curiosity for me just now, BUT are you saying
that if you had multiple slaves running in the background, you are
sure that some of the slaves would be on one of the processors of a
dual processor system and some of the slaves would be on the other
processor? And also the dividing up between the processors would be a
relatively efficient division of resources?
PMJI,
> some of the slaves would be on one of the processors of a dual processor
system and some of the slaves would be on the other processor? <
This would only be the case if the code was specifically written to support
SMP.
> And also the dividing up between the processors would be a relatively
efficient division of resources? <
Actually, it would be efficient. OS/2 runs each VDM in its own thread.
Because of this, the division of labor between processors would be fairly well
balanced.
— James — MAP —
Im only running one slave in the background on a single processor machine. Yes
it does slow down the machine a little, but while you are rending one project
you can continue working on another.
I've noticed a 2-processor machine at my favorite store. Does this imply that
if I were to run 2-3dstudio sessions, I probably would need 32mb of RAM for
each processor, but I could save money on all the other things it would take to
make up 2 complete and separate networked systems: box, harddrive, monitor,
grafx card…
Sounds like a deal I can't pass up.
michael harmon, h3d
Im not shure how dual processor machines work but I dont think you need to get
seprate ram for each processor. but with os/2 warp I think you can run a
seperate copy of 3ds on each processor. I dont think you assign the processor
the os does it on its own.