<h1>Multiple mining pool workers or just one?</h1>

<blockquote>
  <p>It would seem from a server farm administration perspective at least that managing less workers could help simplify some of the configuration and tracking tasks.</p>
</blockquote>

<p>The initial task of configuring the pool and miners is certainly simpler with just one worker name, however, the overall job of administration is made more complex by using that method.</p>

<p>By using a separate worker name for each physical miner (even if you enter it three times, once for each pool in the miner configuration) your job of monitoring is simplified since you can then just check on your pool to see that each miner is performing as expected. Some pools even have alerts if a particular worker's performance drops below a threshold.</p>

<p>By using a separate worker name for each miner you can easily identify a) that there is an issue, and b) which miner has the issue.</p>

<p>You could even label the worker name on each miner to simplify this further.</p>

CC BY-SA 3.0
2018-03-10T02:47:14.060Z
2018-03-10T11:24:25.257Z
2018-03-10T11:24:25.257Z
Willtech
<p>I asked a question about <a href="https://bitcoin.stackexchange.com/questions/72099/what-is-a-worker-exactly-from-antminer-pool-worker-field">What is a worker exactly from Antminer Pool Worker field</a> and got an answer to one of the specific questions within stating that you can generally use a worker name over and over on different machines, and all the work is added together to show the worker's work.</p>

<blockquote>
  <h2>Question</h2>
  
  <p>What factors should be considered for someone trying to decide whether
  to have a worker setup and dedicated to each individual miner device
  versus having one worker setup for multiple miner devices?</p>
</blockquote>

<p>It would seem from a server farm administration perspective at least that managing less workers could help simplify some of the configuration and tracking tasks.</p>

<p>I'm worried doing this one way versus the other could have a negative impact on the ultimate goal to make more money than spent on the electric utility if there's anything applicable that'd affect this.</p>

CC BY-SA 3.0
2018-03-10T02:41:15.267Z
Thank you for addressing separate questions as separate asks.
Willtech
<mining-pools>
Multiple mining pool workers or just one
Pimp Juice IT
# Multiple mining pool workers or just one

(Asked by: username_0 on 2018-03-10)

I asked a question about [What is a worker exactly from Antminer Pool Worker field](https://bitcoin.stackexchange.com/questions/72099/what-is-a-worker-exactly-from-antminer-pool-worker-field) and got an answer to one of the specific questions within stating that you can generally use a worker name over and over on different machines, and all the work is added together to show the worker's work.

> ## Question
>
> What factors should be considered for someone trying to decide whether
> to have a worker setup and dedicated to each individual miner device
> versus having one worker setup for multiple miner devices?

It would seem from a server farm administration perspective at least that managing less workers could help simplify some of the configuration and tracking tasks.

I'm worried doing this one way versus the other could have a negative impact on the ultimate goal to make more money than spent on the electric utility if there's anything applicable that'd affect this.

**Tags:** mining-pools

> **Comments:**
> **username_1**: Thank you for addressing separate questions as separate asks.  

---

## 1 answers

### Answer by username_1 on 2018-03-10. Score: 1 | Accepted answer

# Multiple mining pool workers or just one?

> It would seem from a server farm administration perspective at least that managing less workers could help simplify some of the configuration and tracking tasks.

The initial task of configuring the pool and miners is certainly simpler with just one worker name, however, the overall job of administration is made more complex by using that method.

By using a separate worker name for each physical miner (even if you enter it three times, once for each pool in the miner configuration) your job of monitoring is simplified since you can then just check on your pool to see that each miner is performing as expected. Some pools even have alerts if a particular worker's performance drops below a threshold.

By using a separate worker name for each miner you can easily identify a) that there is an issue, and b) which miner has the issue.

You could even label the worker name on each miner to simplify this further.


---

