I had a blast helping with this project. It was eye-opening on several fronts. Big thanks to @AtlasPool_io and @proofofmike for including me. 1. Atlaspool is faster and more optimized than any node or pool combo you're likely to run at home. And the data shows how fast it is compared to other outside pools. If you want maximum performance, you may as well switch. The realistic goal for self-hosted setups is just getting as close as possible. 2. Your own node probably is not that fast on block notifications. Even with config optimizations, peering makes the biggest difference you can control. Tor only or Tor plus I2P or non-listening nodes adds noticeable lag, probably seconds. I'm testing clearnet only with fast, high peer counts, and it helps so far. You will probably never fully match Atlaspool. It's just better connected than a home node. 3. Rental hashrate changes the picture. Pool mining Datum/Ocean on your own node works great. Solo mining on your own node is not so great. You add extra lag from remote miners falling even further behind on block notifications. 4. Not all pools are equal. The data makes this obvious for both external pools and local instances. Datum edges out the CKpool variants as the fastest locally. The external pool results are strong enough that anyone serious should switch to a better-connected pool immediately. Fun stuff. More people should run this block notification tool and see for themselves. github.com/proofofmike/strat… Always be testing and building and have fun with it.