<p>Having multiple nodes running will help you get connected to more peers. The algorithm behind finding peers takes into consideration a variety of variables, such as the success rate of previous connections, and the IP addresses that get relayed by other nodes. Therefore, the more nodes you have running, the better the chances of connecting to different peers.</p>

<p>This means that it doesn't really matter that they're running on different operating systems. You can run different nodes on the same OS, on different ports. This would effectively be the same as running them on different virtual machines.</p>

<p>What matters here is the high peer connection rate, which can be accomplished by running many nodes on different ports.</p>

CC BY-SA 3.0
2014-05-19T15:02:27.807Z
Oh, right, yeah, so I could even run multiple bitcoind instances on the same OS? (of course all with different bitcoin settings and work dir) That would be even better!
RocketNuts
CC BY-SA 3.0
2014-05-19T15:02:52.117Z
I guess they'd also need their own copy of the blockchain, they probably can't share that data accross multiple instances? :)
RocketNuts
CC BY-SA 3.0
2014-05-19T15:25:29.467Z
By the way, now that I think of it, if I have 2 or more bitcoind daemons running (each with their own datadir, config, port, etc), and interact with them from the command line interface (like "bitcoind getinfo" etc) how would I identify which bitcoind instance I'm referring to?
RocketNuts
CC BY-SA 3.0
2014-05-20T07:33:00.717Z
I'd recommend creating a separate user account for every bitcoind. Then, you just log in (or `su`) to any account and run `bitcoind getinfo` on that particular instance. That's how I do it :-)
knaperek
CC BY-SA 3.0
2014-05-19T12:37:53.687Z
2014-05-19T12:53:18.257Z
2014-05-19T12:53:18.257Z
Luca Matteis
<p>I've got a server running 24/7 with lots of resources left. I want to run a full Bitcoin node, but actually, I thought of running a few virtual machines on it (using virtualbox) and running a full Bitcoin node in each of them.</p>

<p>Obviously they'd all need to use different ports (which are to be forwarded to the particular VM LAN IPs by my router). </p>

<p>Will that work, i.e. would they be on different 'metric locations' in the Bitcoin network? (even though they have the same physical location and same IP of course)</p>

<p>Reason for this endeavour: being 'as connected as possible' to different parts of the network simultaneously, just as if I had multiple nodes running on different physical locations throughout the world.</p>

<bitcoind><network><nodes><port>
Running multiple BTC nodes on separate VMs on the same host machine?
RocketNuts
# Running multiple BTC nodes on separate VMs on the same host machine?

(Asked by: username_0 on 2014-05-19)

I've got a server running 24/7 with lots of resources left. I want to run a full Bitcoin node, but actually, I thought of running a few virtual machines on it (using virtualbox) and running a full Bitcoin node in each of them.

Obviously they'd all need to use different ports (which are to be forwarded to the particular VM LAN IPs by my router).

Will that work, i.e. would they be on different 'metric locations' in the Bitcoin network? (even though they have the same physical location and same IP of course)

Reason for this endeavour: being 'as connected as possible' to different parts of the network simultaneously, just as if I had multiple nodes running on different physical locations throughout the world.

**Tags:** bitcoind, network, nodes, port


---

## 1 answers

### Answer by username_1 on 2014-05-19. Score: 3

Having multiple nodes running will help you get connected to more peers. The algorithm behind finding peers takes into consideration a variety of variables, such as the success rate of previous connections, and the IP addresses that get relayed by other nodes. Therefore, the more nodes you have running, the better the chances of connecting to different peers.

This means that it doesn't really matter that they're running on different operating systems. You can run different nodes on the same OS, on different ports. This would effectively be the same as running them on different virtual machines.

What matters here is the high peer connection rate, which can be accomplished by running many nodes on different ports.

> **Comments:**
> **username_0**: Oh, right, yeah, so I could even run multiple bitcoind instances on the same OS? (of course all with different bitcoin settings and work dir) That would be even better!  
> **username_0**: I guess they'd also need their own copy of the blockchain, they probably can't share that data accross multiple instances? :)  
> **username_0**: By the way, now that I think of it, if I have 2 or more bitcoind daemons running (each with their own datadir, config, port, etc), and interact with them from the command line interface (like "bitcoind getinfo" etc) how would I identify which bitcoind instance I'm referring to?  
> **username_2**: I'd recommend creating a separate user account for every bitcoind. Then, you just log in (or `su`) to any account and run `bitcoind getinfo` on that particular instance. That's how I do it :-)  

---

