Loading...
> >

multiple DAZ instances rendering at the same time?

Noved1Noved1 Posts: 160
edited August 2013 in New Users

hey, just a quick question, what if i were to create a few scenes in daz, and then save them, and then click to open daz a few times, and have multiple DAZ's running, and rendering all the different scenes at the same time, so that i could have many renders made all in the same time frame. would that at all work out?
or would it...fry my poor PC?---thank you for your time.

Post edited by Noved1 on

Comments

  • Lissa_xyzLissa_xyz Posts: 6,116
    edited December 1969

    Your PC may blow up.

    lol Really though I'm not sure if that's even possible. I know you can have Daz and Poser open rendering at the same time, pc specs dependent of course. Can't say I've tried multiple DS renders at once.

  • Noved1Noved1 Posts: 160
    edited December 1969

    well, i have two daz programs running at once, and i am bouncing back and forth setting up two scenes. it seems fully workable to render, although its going to take up my entire pc, i am sure of it

  • Lissa_xyzLissa_xyz Posts: 6,116
    edited August 2013

    Depending on your system specs, render settings, and your scene setup, one of those renders alone can eat your system resources.

    Post edited by Lissa_xyz on
  • Richard HaseltineRichard Haseltine Posts: 100,948
    edited December 1969

    There wouldn't be any great advantage in having multiple DSes rendering since each can use all of the available resources - if anything I suspect that the net result of multi-rendering would be slower than letting DS do the job, unless you are wanting to leave the system munching through multiple renders (and even then, a script could render through all the scenes in a set folder fairly easily).

    When running multiple instances of the same version of DS remember that starting, stopping or doing a File>New or File>Open will clear the temp folder, including the converted .tdl image files used by 3Delight - which would kill any current renders in other instances.

  • SiscaSisca Posts: 875
    edited December 1969

    If you're rendering using 3Delight then I'd say it'd probably end up crashing all of the instances depending on how complex your scenes are and how much memory you have. 3Delight will use up 100% of the CPU cycles you give it and with a more complex scene with lots of reflection/transmaps can fill up memory. When memory gets full it almost always crashes DS, at least it does for me.

    As Richard said above, even if you don't end up crashing you're probably going to end up taking longer to render all of the scenes than if you did them individually.

    From a programming point of view, while most modern windows programs will let you run multiple instances it's not usually a good idea to do so unless the app was specifically designed to do so. Applications tend to create temp files to act kind of like a scratch pad and most of the time they put these files in the same place. Having multiple copies of the same application writing these temp files to the same location at potentially the same time is a recipe for disaster.

    This is especially true for things like the CMS database if any database writes weren't designed to be tolerant of collisions you risk corrupting the database if 2 instances attempt to write at the same time. For programs that were designed to have multiple instances running the programmer knew this could be an issue and coded for it. For a single instance program they might not have thought of it.

  • adamr001adamr001 Posts: 1,322
    edited December 1969

    There are ways to make it work, if you really, really had to. CPU affinity for example. You could split up the cores each instance of DS is assigned to so that they weren't stepping on each other. You still run into memory contention and whatnot, but it's definitely something you *could* do, just not sure it's something that's worth doing.

Sign In or Register to comment.