message queue - PHP Job queueing: One uber-worker/dispatcher or many smaller workers? -

I'm starting to use asynchronous jobs / messages so that the user does some heavy background work on the PHP page rather than creating a page Waiting for it and waiting for it So far, I'm leaning towards using Rainbartck on the Rainbow MQ or Amazon's SQLS, but my question below is a bit more common and applies to all of them:

For many types of jobs

• The worker looks at all jobs, representative on the basis of the job type
• Only open connection to beenstalked
• Use meta-data
• Only 1 operation can process on the server at a time

• Each worker only sees one type of job
• Multiple, continuous connections for Beanstock
• Less complexity, / Li>
• One works
• more work
Many other factors I also do not know about, therefore Any additional suggestions will be appreciated.

(If it matters, I plan to run a daemon-ijs of PHP-based worker script through Supervisor, for now the worker must have been running on only 1 server, but it will be two in the future. Can increase ...)