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 ?

Hey everyone,

I started my own pools because I was tired of random issues happening on all the push-pools I've been apart of.

- Dallas, TX Linux servers
- 0% fee on all pools
- PPLNS
- up to date versions
- No locally stored coins

User: Your coin address
Pass: x

http://hashville.io/


This is a solo project of mine, so I will be updating the frontend to be more aesthetically pleasing moving forward.

If you have questions, suggestions or comments please feel free to post/ask me.

New as a registered user, long time lurker, figured it was time since I'm getting pretty deep into mining now.

It's easy to learn a lot of new things on this website, I'm hoping I can contribute as well.