Hi, I have problem, when i want to partition particles with krakatoa and send them all to deadline, all partitions (or max instances) start on first core and this means all other cores ale not used and the simulation is realy slow. So i must click on all instances of 3dsmax and set then manualy to use only one different processor core. Is there some automaticsolution directly in deadline?
The affinity can be set by Deadline, but by default all tasks should have access to all cores. Windows would then load all cores automatically as multiple Max instances are launched.
You can select a slave(s) while in SuperUser Mode, right click and select “Modify Slave Settings”:
thinkboxsoftware.com/deadlin … esettings/
Check to see if the slave was set explicitly to Affinity to specific cores.
On sorry, for my mystake, i meant that when i send to deadline taks to compute 10 partitions on one computer the slave start to compute it on all processors (which is automatic affinity), but in reality all partitions (max instances) are computet on first core, so it is realy slow, but when i change affinity and manualy assign different core for different 3dsmax instance in tasjk manager, the computation is realy fast. So i donk know if there is some automated method to force new instance of max to be calculated on core which dont use max instance, if you understand. If you have time you can try it, maybe it is windows problem i donk know
Thanks a lot.
I’m not all that familiar with how the partitions are submitted to Deadline, but if they are submitted as a single job with concurrent tasks higher than 1 (ie: concurrent tasks equal to the number of partitions), then you can probably enable the “One Cpu Per Task” option under the Options tab in the Deadline submitter. If I’m not mistaken, the Krakatoa submitter pulls settings from regular Deadline submitter.
I’ll let Bobo confirm whether or not this will actually help. 
I think this is a 3dsmax and/or Windows issue, but we added that “One Cpu Per Task” option because another client was running into a similar problem.
Cheers,
- Ryan
The “One CPU Per Task” option in the “Options” tab of the SMTD dialog should work with Krakatoa submissions - Krakatoa only overrides some SMTD settings that need to be changed specifically for partitioning, but all other settings should stick. So try opening the SMTD dialog, checking the “One Cpu Per Task” option and then opening the Krakatoa GUI and submitting the Partitions.
I will expose the “One CPU Per Task” option directly in the Krakatoa “Partitioning” rollout in a future update (probably in Krakatoa MX 2.1).