I also tested that frontend for the p2pool but it was eating my RAM if I left it open on the browser so I went back to the old and just did some modifications so it looked pretier hehe, as it doesnt do any kind of managment you dont really need something very pretty as longs as the stats are readable enough. One thing Im trying to setup is an option to search your own BTC address so you dont need to go throught the whole list.
I was thinking the same thing, that's the only shortcoming
I think the extended frontend only eats your RAM if you set it to auto-refresh, but I've not looked in to it, is that what you found?
For the server storage I know there is a hosting in France that for around 15 euros per month you will quite a good server with 1 tb of hard drive and 5 tb of traffic, then you can update it for more traffice, power, etc ....
About the latency between the p2pool and the bitcoind thats probably a hardware resources problem, bitcoind uses quite a lot of RAM (at least the one Im running in windows 24/7 uses around 500-700 mb) and some disk. I would recommend you to run a light version of Debian (my basic installation of debian only uses 60mb of RAM) to get the best of your hardware. Remenber that using litecoind and bitcoind will take a lot of resources by thenselves. If in the end you go for a normal pool you will also need to get in count the database cpu/RAM usage.
I also switched to p2pool as to get a stand-alone pool you need quite some gigahashes to actually get something. Even p2pool get only one or two or even none blocks per day with 1Ths.
Do you know what that host is? And do they use SSDs? If it's a hardware problem it's not the RAM as I'm only using 60% of it, do you know whether the communication between bitcoind/p2pool needs to be written to disk? Because right now if it's not a software problem I think the only thing it could be is an IO disk read/write capacity problem
it's very strange, it seems to add 4s latency all at once every 12 hours. I added a well known node but it hasn't had any effect. I was kinda hoping I could figure some patch for bitcoind to work around that or that 8.0.2 would fix the problem