Swarm "Busy, Unassigned" in small Dev team enviroment

Development Rendering
, , , , , ,
1

We have Swarm setup and the Coordinator is able to see all the machines, pings are all successful and if a light build is initiated on a machine, it will output too all machines - If they are not being used.

The problem we have is we want Swarm to use a couple of cores from each machine whilst we are using them for other things.

For example: 2 machines running Photoshop will appear as busy in the coordinator yet in the task manager, the CPU is at 10% max and ram usage is at about 15%…

  1. Is there anyway of getting Swarm to use the rest of the machine, or half of the available computing power?

  2. What are the requirements for the Swarm Agent to declare a machine “Too Busy” for any Swarm rendering

2

  1. from my experience, if its unassigned, and the agent is running, it will get a job assigned, no matter if its busy, but not 100% sure. But it wont get disrupted if it’s runnig gonce, so maybe if you are baking, just tell the people to stop doing stuff for a second? :smiley:

  2. Yes, In your SwarmAgent under the settings tab, there is a “Developer Settings” area, toggle to true to unhide the DeveloperSettings-Tab, there you can set the LocalJobsDefaultprocessorCount and RemoteJobsDefaultProcessorCount to the number of cores you want it to use.

3

There are several questions to this problem here.I post my solution here in a random post

In my case I realized that svchost.exe was running at 25% CPU power which caused the busy status. I went to find out more about this process here and installed the ProcessExplorer to analyze it. In my case it turned out that the Windows update service was consuming all the power. I didn’t allow updates to be installed automatically but it had some updates waiting. Once I turned “check for updates” off and restarted, the 25% load disappeared and the agent reports as “Available” now.
Hopefully this will help someone with the same problem

4

Hi all. I just cleared the SWARMCACHE Folder and it ran again