In dspConduct, you can route events from the content webapps to separate queues, but once back in Conduct, everything is grouped together in the same queue.
I made a simple change to the procedure that creates jobs in conduct to route the job to queues based on the webapp that triggered the request. The queues are maintained in my Param table within each content web app.
This helps with throughput and competition for resources.
what is the problem that led you towards making this customization. Too many jobs in the same queue with not enough threads?
adding more threads to the service and queues could also achieve the same results. The out of the box max threads is not necessarily a true max thread count for your server.