What's the proper way to scale p2pool? 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:


Create a cloud load balancer for the APP servers
Take a server snapshot of my single APP server
Spin up 2 more servers from that server snapshot and place them behind the load balancer
Update the DNS to point to the floating IP of the load balancer


Is this the proper way to scale up p2pool ?
Disclaimer: There is no "proper" way to do anything :)

Some people think that P2Pool is hard to scale. But it can be scaled easily by dividing it into smaller pools that feed into the main pool.

This is beneficial for a lot of reasons but two important ones that come to mind are hardware restrictions (like what you seem to be getting into) and small miners being unable to revive payouts because of P2Pool's sharechain's difficulty.

This could be done any number of times, in a peer-to-peer way to achieve an acceptable difficulty; and eventually it will have to be done multiple times, if, for example, the P2Pool difficulty is in the petahashes, and people are still mining in the kilohashes

This could also be done with non-peer-to-peer, "standard" pools (and has been done), by having them feed into the P2Pool network.