user7281: Some bitcoin mining clients mine on a single worker, while other clients allow multiple workers.  How will either of these options affect mining production?

user11796: Bitcoin is generating using your hardware, thus if you have 1 worker on a 5 GHS piece of hardware, then your single worker runs at 5 GHS. If you add yet another worker , your'e complicating the issue for no real good reason. The two workers have to share the 5 GHS resources and each worker will perform at Approximately 2.5 GHS.
If you add 100 workers then none of your workers will perform properly.
I would recommend using one worker per hardware unit. 

user6321: Depends. Generally you'd use multiple workers when you have multiple machines (ie graphics cards, mining rigs, or a farm of USB sticks). In some cases you could have them all combined and contributing to a single worker but usually this is not desirable because you'd want to keep track of how each device is performing.  
If for no other reason, that certainly makes it easier to tell which one has crashed or is not working when problems arise. 
Some hardware&software combinations might produce slightly more from running on two workers at once but in most cases I think that's unlikely. 

7281: <p>Some bitcoin mining clients mine on a single worker, while other clients allow multiple workers.  How will either of these options affect mining production?</p>
 11796: <p>Bitcoin is generating using your hardware, thus if you have 1 worker on a 5 GHS piece of hardware, then your single worker runs at 5 GHS. If you add yet another worker , your'e complicating the issue for no real good reason. The two workers have to share the 5 GHS resources and each worker will perform at Approximately 2.5 GHS.</p>

<p>If you add 100 workers then none of your workers will perform properly.</p>

<p>I would recommend using one worker per hardware unit. </p>
 6321: <p>Depends. Generally you'd use multiple workers when you have multiple machines (ie graphics cards, mining rigs, or a farm of USB sticks). In some cases you <em>could</em> have them all combined and contributing to a single worker but usually this is not desirable because you'd want to keep track of how each device is performing.  </p>

<p>If for no other reason, that certainly makes it easier to tell which one has crashed or is not working when problems arise. </p>

<p>Some hardware&amp;software combinations might produce slightly more from running on two workers at once but in most cases I think that's unlikely. </p>
