just a quick question , their is no way \ plan to Multhithreat the Saving PRt Data from krakatoa ? i m testing it with the latest version of the beta Rc3 i think and it seems to all be Single treated the “Updating the Particles” render pass…
The “Updating Particles” phase is not something Krakatoa itself does. It just asks the particle systems in the scene to update and waits until they are done. For example, PFlow is generally single-threaded and there is nothing we can do about it. If TP is multi-threaded, Krakatoa would benefit from it. This is the same with any renderer that wants to render particles - it asks for them and waits until they are ready to render.
Once the particles are updated by the host particle system, getting them and saving them is relatively fast, but AFAIK it cannot be multi-threaded much. We have multi-threaded the loading, shading and culling of PRTs for the next version as you saw on our “olympic” videos.
Once again, in the case of PFlow, if the particles are already updated once and PFlow does not need to update its own caches, getting and saving the particles from it is really fast. (I am giving PFlow as example because I have more experience with it, I know you don’t use it).
This is another reason we are using Partitioning. Instead of calculating 10M particles in a single thread, we can send 10 tasks with 1M each to Deadline and would get the same amount of particles in 1/10 of the time, using 10 CPUs. In fact, Deadline allows us to run one Krakatoa on each CPU, so one can use a Quad machine to do 4 partitions in parallel by dequeing 4 tasks at once (in the “Single Job, Task Per Partition” mode) as long as the memory allows it.
interesting… thanks for answering… i m starting to test it hard (i know it might be too late for 1.2 ) but still i got some major things i m finding between tp and krakatoa … i will start writing them down…
Actually, there is no 1.2 Beta at this point. It never really started.
What you are running is probably 1.1.1 or 1.1.2 (which we posted last week).
We will be doing a 1.5 Beta (or something like that) by the end of the year with a large number of new features.
We know that the connection with TP is rather sketchy, but please feel free to write down everything you find and send it our way.
will do , yes your right sorry for the wrong posting… i read 1.1.2 but ringed in my head as 1.2 … oups ! 