Topic: What's the proper way to scale p2pool? (Read 967 times)
p2pool is decentralized. Just fire up another node at the point of use.
At the moment I have ONE linux server acting as the "APP" server for bitcoind/p2pool applications and another linux server with nginx proxying web traffic from the APP server, while behind CloudFlare.
What would be the proper way to scale out p2pool in this scenario? My thoughts were:
1. Create a cloud load balancer for the APP servers
2. Take a server snapshot of my single APP server
3. Spin up 2 more servers from that server snapshot and place them behind the load balancer
4. Update the DNS to point to the floating IP of the load balancer
Is this the proper way to scale up p2pool ?
What would be the proper way to scale out p2pool in this scenario? My thoughts were:
1. Create a cloud load balancer for the APP servers
2. Take a server snapshot of my single APP server
3. Spin up 2 more servers from that server snapshot and place them behind the load balancer
4. Update the DNS to point to the floating IP of the load balancer
Is this the proper way to scale up p2pool ?
Jump to: