Run multiple JobProcessor.exe on the same Machine

[Michael_Noehrer]

Current Situation: A single machine can only run a single instance of JobProcessor.exe.
Makes it difficult to react to additional loads caused by an increased amount of submitted jobs
Adding new machines is not always feasible, especially when it come to handle spikes in submitted jobs. 

Proposal: Add the ability to run multiple instances of JobProcessor.exe on the same machine.
This would: Increase flexibility when it comes to configuring accepted jobs & Give us more flexibility in load balancing.

[Hunteil]

Maybe a limitation b/c of licenses. Also maybe a limitation of how many of those background programs can run. Also depending on computer, the job processor can really slow down your system. Something I found that helped was increasing the interval that the job processor checks for work in the queue.

[thomas.behrendY5FX4]

Also, it depends on the jobs you run, if you start ACAD or Inventor, you can´t run them in parallel. Our experience is, let it run as a single instance and if you need a second one, boot up a second virtual machine on a different system.

[DavidWarta]

This would be amazing, as most job processors are not very multithreaded and if the machine has enough memory to run multiple job processors it could easily speed up processes. or even set the priority between different job processors on a single machine. For example, have one with high priority doing property sync and update rev blocks and another generate the pdf and dwf files.

[thomas.behrendY5FX4]

In theory, you can do that already when using tasks
First task is updating everything, you wait for it. Second and third task
is creating files, they can run parallel.

Sadly I don't work there anymore, so I can't give you an example. But we
tried something like that and it worked so good, we put it in production
for Inventor files.