[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[windpath]

Hey Good afternoon!, I need some help as there is not a central support line. I believe my miner may not be running Getblock, I think it's running getwork. The pool shows that I'm connected and hashing, The Issue I'm having is that my miner is registering that Shares are being accepted but nothing registers under my payout address. Is there some time you have to wait, is there an error on my end, can anyone help me out, thanks!

P2Pool will accept (but not consider valid) shares below the minimum difficulty in order to better estimate your hashrate and payout.

It should give you an estimated time to share after your hash rate has been established.

Until you submit a share that meets the minimum difficulty, and the pool subsequently finds a block, you will not receive a payout.

[bitlock1]

Is there a way to minimize or increase performance on either bitcoin or p2pool

Warning: LOST CONTACT WITH BITCOIND for 1.8 minutes! Check that it isn't frozen or dead

The stats on my p2pool for bitcoin are really slow

bitcoind and p2pool are running on the same machine

thx

[frodocooper]

Is there a way to minimize or increase performance on either bitcoin or p2pool

Warning: LOST CONTACT WITH BITCOIND for 1.8 minutes! Check that it isn't frozen or dead

The stats on my p2pool for bitcoin are really slow

bitcoind and p2pool are running on the same machine

thx

See gyverlb's guide for tips on how to maximize your P2Pool node's performance. It may be a little outdated, but most of the tips and pointers there still hold true today.

Please ignore the bits that suggest setting and tuning a blockmaxsize value. The blockmaxsize parameter has been deprecated in favor of the blockmaxweight parameter, which you should set to a suggested maximum of 3950000.

If you have a system with a reasonably fast CPU (one with a base clock of at least 2.4 GHz) and at least 4 GB of RAM, you may want to try out jtoomim's 1mb_segwit fork, if you aren't already, which promises better overall performance and reward fairness. Using PyPy to run 1mb_segwit is highly recommended for maximum performance.

[tubexc]

Is there a way to minimize or increase performance on either bitcoin or p2pool

Warning: LOST CONTACT WITH BITCOIND for 1.8 minutes! Check that it isn't frozen or dead

The stats on my p2pool for bitcoin are really slow

bitcoind and p2pool are running on the same machine

thx

Hi
Usually that's a RAM problem. You may want to install a 64 bit based OS so you can add more RAM or if
you have the budget you can rent a Vps.
Happy mining

[bitlock1]

Thanks,

I have plenty of ram on this system, before I try a new fork would this be a bitcoind ram issue or p2pool ram issue and what setting would I set to give the program a little more breathing room.

thanks,

[bitlock1]

Thanks for the blockmaxweight tip - I was using the old suggestions.

>>>>>
Please ignore the bits that suggest setting and tuning a blockmaxsize value. The blockmaxsize parameter has been deprecated in favor of the blockmaxweight parameter, which you should set to a suggested maximum of 3950000.

If you have a system with a reasonably fast CPU (one with a base clock of at least 2.4 GHz) and at least 4 GB of RAM, you may want to try out jtoomim's 1mb_segwit fork, if you aren't already, which promises better overall performance and reward fairness. Using PyPy to run 1mb_segwit is highly recommended for maximum performance.
<<<<<

[frodocooper]

I have plenty of ram on this system, before I try a new fork would this be a bitcoind ram issue or p2pool ram issue and what setting would I set to give the program a little more breathing room.

There isn't much you can do about P2Pool's RAM usage, as there is no user-accessible way to manage it.

You may refer to this guide if you're interested in tuning bitcoind's memory usage. Note that in Bitcoin Core 0.14.1 and later, the default dbcache value is 450, and not 300 as stated in the guide.

[tubexc]

Strange, p2pool general failures.I had never seen this before 

[Rabinovitch]

https://en.bitcoin.it/wiki/P2Pool#Stales

Could anybody be so kind to explain in more details, what does this mean?

On P2Pool stales refer to shares which can't make it into the sharechain. Because the sharechain is 20 times faster than the Bitcoin chain many stales are common and expected. However, because the payout is PPLNS only your stale rate relative to other nodes is relevant; the absolute rate is not.

What's PPLNS got to do with it?

[bitlock1]

I have switched over to https://github.com/jtoomim/p2pool  code and things seem better, but still occasionally  see bitcoind not responding errors.

I review the bitcoind logs

Code:

receive version message: /P2Pool:17.0-4-g68f653f-dirty/: version 70002, blocks=0, us=127.0.0.1:8333, peer=41
2017-12-08 16:01:59 Misbehaving: 127.0.0.1:52702 peer=41 (0 -> 100) BAN THRESHOLD EXCEEDED
2017-12-08 16:01:59 Warning: not banning local peer 127.0.0.1:52702!

i can increase the banscore index to 150 ? not sure if this is a good move. Any Suggestions?

current bitcoin.conf file

Code:

rpcuser=bitcoinusernamegoeshere
rpcpassword=bigolpasswordgoeshere
#----
#rpcallowip=127.0.0.1
#----
listen=1
server=1
daemon=1
maxconnections=20
#blockmaxsize=1000000 #default is 500000 (deprecated)
blockmaxweight=3950000
mintxfee=0.00001
minrelaytxfee=0.00001
dbcache=500
maxmempool=500
rpcthreads=50
addnode=v4.us-west.fibre.bitcoinrelaynetwork.org
#--------------------

Moderator note: frodocooper edited this post to include code tags.

[jtoomim]

bitlock1, it sounds like your machine is just too slow for bitcoind+p2pool. Please list your machine's specs, including CPU model, amount of RAM, type of disk (SSD vs HDD), and OS. It would also be helpful if you could list your node's IP address or post a screenshot of your "Bitcoind GetBlockTemplate Latency" and "Memory Usage" charts. Output while using the "--bench" command-line option is also helpful.

Usually, the "bitcoind not responding" error happens when bitcoind is responding just fine, but p2pool's queue of tasks to perform grows faster than the CPU can perform those tasks. This causes p2pool to take several minutes before p2pool processes the response from bitcoind, even though bitcoind may have responded within milliseconds. This can either be caused by running out of RAM (resulting in swapping to disk) or by a slow CPU (e.g. anything from AMD before Ryzen).

Currently, p2pool requires a fast CPU with good single-threaded performance. I wish this weren't the case, but the cost in programmer time of fixing it is about the same as buying all p2pool users a faster CPU. I've made several improvements already towards that goal, but clearly not enough.

[bitlock1]

AMD Opteron 6128 - python is running near 100% so pypy may have to be my route as this processor may be a little weak even with 8 cores
32GB Memory
Hard Drive may be a 5400rpm - this was an old server that I revived and i just grabbed a 1TB HD I had, could have probably used a SSD

I didn't realize  this was going to be so intensive ... I may have to rebuild, but will give pypy a try 1st

Bitcoind GetBlockTemplate Latency is bad - mean of 9.07 seconds
Memory Usage is about 1.9GB

However this server is also server a Dash Node and a Litecoin node and running as expected.
Latency is around .0201s on the Dash node with memory of 235MB, and about .0668s on the Litecoin node with memory of 1.26gb

I am also not sure what version of your code I am using, terrible with git, what would be the command to change from
jtoomim/p2pool
to
https://github.com/jtoomim/p2pool/tree/1mb_segwit.git
if that is the current version I should use.

--bench has been added, will supply debug.log shortly.

thanks

[jtoomim]

Yeah, an Opteron 6128 is way too slow for bitcoin p2pool. Sorry. It doesn't matter how many cores it has; it's a 2 GHz pre-Ryzen AMD CPU, and that's nowhere near fast enough. A cheap dual core Core i3 would be much better than an 8-core AMD server chip. Pypy will help, but I expect you'll still have problems even with pypy.

Dash and Litecoin should work fine. Most of the CPU load comes from dealing with transactions, and neither Dash nor Litecoin have much transaction volume.

The HDD should be fine. I wouldn't worry about upgrading that. If you are thinking of mining Ethereum, you'd need an SSD, but an HDD should be okay for Bitcoin, especially if you use -dbcache=8000 on bitcoind (you have the RAM, might as well use it).

[bitlock1]

jtoomim,

I setup pypy and it is running about the same - so will try this for a few days and see if my latency drops.

It looks like I was running the forest master branch after researching git somewhat.

Are you still suggesting to run your 1mb_segwit branch?

thanks

[Cryptonomist]

Hello,

I've recently switched from the main p2pool to jtoomim's fork, due to issues with cpu load. P2Pool works, and I can mine, but over time my node start creating huge amounts of orphans. An analysis of the problem showed that the issue was the cpu load. It's nearly always at 100%. I also saw the same messages that other people on this forum had, namely that the connection with bitcoind was lost. It is indeed so that this starts to happen when the cpu utilization is at 100% for a very long time. I must say that this became only quite recently an issue for me. I've been using p2pool for over a year now, but it is only the last couple of weeks that the cpu utilization became an issue. At first I used just python to run p2pool, and this was sufficient. Recently I switched to pypy as an attempt to alleviated the problem with the cpu load. This diminished the cpu load slightly, however not sufficiently, and my node still gets a lot of orphan shares (the stale rate is enormous: between 30 and 50%). So at that point I decided to switch to jtoomim's fork because of the optimalizations.

However I experience some problems. Well actually I haven't been able to mine at all with jtoomim's fork. Somehow my miners don't mine. I know the miners work and so does the setup because I can mine 'perfectly' on the main P2pool. But when using jtoomim's fork all the work of my miners get rejected. I also see the lights flashing on the usb miners, so they are active.

Cgminer gives me the following:

Code:

[2017-12-09 12:37:24.975] Pool 0 difficulty changed to 318767.1
 [2017-12-09 12:37:24.976] Stratum from pool 0 requested work restart
 [2017-12-09 12:38:00.753] Pool 0 difficulty changed to 316516.4
 [2017-12-09 12:38:00.753] Stratum from pool 0 requested work restart
 [2017-12-09 12:38:53.471] Pool 0 difficulty changed to 311201.8
 [2017-12-09 12:38:53.471] Stratum from pool 0 requested work restart
 [2017-12-09 12:39:21.296] Pool 0 difficulty changed to 308553.9
 [2017-12-09 12:39:21.297] Stratum from pool 0 requested work restart
 [2017-12-09 12:39:44.927] Pool 0 difficulty changed to 305991.7
 [2017-12-09 12:39:44.927] Stratum from pool 0 requested work restart
 [2017-12-09 12:39:46.181] Stratum from pool 0 requested work restart
 [2017-12-09 12:40:08.425] Pool 0 difficulty changed to 304497.7
 [2017-12-09 12:40:08.426] Stratum from pool 0 requested work restart
 [2017-12-09 12:40:08.426] Stratum from pool 0 requested work restart
 [2017-12-09 12:40:10.956] Stratum from pool 0 requested work restart
 [2017-12-09 12:40:13.911] Stratum from pool 0 requested work restart
 [2017-12-09 12:40:28.796] Pool 0 difficulty changed to 303616.9
 [2017-12-09 12:40:28.796] Stratum from pool 0 detected new block at height 498385
 [2017-12-09 12:40:41.587] Pool 0 difficulty changed to 301658.7
 [2017-12-09 12:40:41.587] Stratum from pool 0 requested work restart
 [2017-12-09 12:40:49.738] Pool 0 difficulty changed to 301019.8
 [2017-12-09 12:40:49.738] Stratum from pool 0 requested work restart
 [2017-12-09 12:40:52.193] Pool 0 difficulty changed to 331502.0
 [2017-12-09 12:40:52.193] Stratum from pool 0 requested work restart
 [2017-12-09 12:41:01.276] Stratum from pool 0 requested work restart
 [2017-12-09 12:41:05.722] Stratum from pool 0 detected new block at height 498386
 [2017-12-09 12:41:07.698] Pool 0 difficulty changed to 344825.9
 [2017-12-09 12:41:07.698] Stratum from pool 0 requested work restart
 [2017-12-09 12:41:39.337] Pool 0 difficulty changed to 343068.6
 [2017-12-09 12:41:39.337] Stratum from pool 0 requested work restart
 [2017-12-09 12:42:02.765] Pool 0 difficulty changed to 338019.6
 [2017-12-09 12:42:02.765] Stratum from pool 0 requested work restart
 [2017-12-09 12:42:02.765] Stratum from pool 0 requested work restart
 [2017-12-09 12:42:20.844] Pool 0 difficulty changed to 336936.5
 [2017-12-09 12:42:20.845] Stratum from pool 0 requested work restart
 [2017-12-09 12:42:53.143] Pool 0 difficulty changed to 335038.0
 [2017-12-09 12:42:53.144] Stratum from pool 0 requested work restart
 [2017-12-09 12:43:07.531] Pool 0 difficulty changed to 334145.2
 [2017-12-09 12:43:07.531] Stratum from pool 0 requested work restart
 [2017-12-09 12:43:11.495] Stratum from pool 0 requested work restart
 [2017-12-09 12:43:27.773] Pool 0 difficulty changed to 331792.9
 [2017-12-09 12:43:27.773] Stratum from pool 0 requested work restart
 [2017-12-09 12:43:46.130] Pool 0 difficulty changed to 330480.7
 [2017-12-09 12:43:46.130] Stratum from pool 0 requested work restart
 [2017-12-09 12:44:45.373] Pool 0 difficulty changed to 322995.3
 [2017-12-09 12:44:45.373] Stratum from pool 0 requested work restart
 [2017-12-09 12:44:48.620] Stratum from pool 0 detected new block at height 498387

That is all I get. Also accepted = 0 and rejected = a lot.

If I analyze the output of p2pool, I see the following:

Code:

2017-12-09 12:46:42.790786  Pool: 5909TH/s Stale rate: 4.8% Expected time to block: 13.4 days
2017-12-09 12:46:44.605121 Peer sent entire transaction 7f7e027bf783f74f0004f84945fa0ad4e811dea0f77653ed26646facef7ab012 that was already received
2017-12-09 12:46:50.004147 Peer sent entire transaction b1dbf883f527584830abcd8cc2ed37db0bfc7f0e9cd0a6ea73558577a1641214 that was already received
2017-12-09 12:46:51.680249 Peer sent entire transaction b1dbf883f527584830abcd8cc2ed37db0bfc7f0e9cd0a6ea73558577a1641214 that was already received
2017-12-09 12:46:54.528876 Peer sent entire transaction e21cbec550ca962e08a9e630d9192e1ff3813ab158b5d9882ed8c0a406128614 that was already received
2017-12-09 12:46:55.393046 Peer sent entire transaction b1dbf883f527584830abcd8cc2ed37db0bfc7f0e9cd0a6ea73558577a1641214 that was already received
2017-12-09 12:47:00.150376 Peer sent entire transaction b1dbf883f527584830abcd8cc2ed37db0bfc7f0e9cd0a6ea73558577a1641214 that was already received
2017-12-09 12:47:00.306119 Peer sent entire transaction 24c5c38682bfe425d1317d6b56d83ef1e3b04f732450f8b7f8131ad90842fa39 that was already received
2017-12-09 12:47:04.560185 Peer sent entire transaction ad2f5f371325641b5f8e5db13c2d62826104414beaef2f26e987c0f9baa36149 that was already received
2017-12-09 12:47:04.951282 Peer sent entire transaction 24c5c38682bfe425d1317d6b56d83ef1e3b04f732450f8b7f8131ad90842fa39 that was already received
2017-12-09 12:47:08.196591 Peer sent entire transaction 24c5c38682bfe425d1317d6b56d83ef1e3b04f732450f8b7f8131ad90842fa39 that was already received
2017-12-09 12:47:10.547186 Peer sent entire transaction 24c5c38682bfe425d1317d6b56d83ef1e3b04f732450f8b7f8131ad90842fa39 that was already received
2017-12-09 12:47:10.624559 Peer sent entire transaction 24c5c38682bfe425d1317d6b56d83ef1e3b04f732450f8b7f8131ad90842fa39 that was already received
2017-12-09 12:47:12.794002 P2Pool: 18894 shares in chain (10338 verified/18895 total) Peers: 7 (1 incoming)
2017-12-09 12:47:12.794440  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2017-12-09 12:47:12.794901  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: (0.0000)=0.0000 BTC
2017-12-09 12:47:12.795191  Pool: 5909TH/s Stale rate: 4.8% Expected time to block: 13.4 days
2017-12-09 12:47:14.620279 Peer sent entire transaction 55b649247f4f1c3401dff5ab149f1363821c6c26b39e0e9344b9e6c04b968277 that was already received
2017-12-09 12:47:16.179862 Peer sent entire transaction 55b649247f4f1c3401dff5ab149f1363821c6c26b39e0e9344b9e6c04b968277 that was already received
2017-12-09 12:47:20.354942 Peer sent entire transaction 55b649247f4f1c3401dff5ab149f1363821c6c26b39e0e9344b9e6c04b968277 that was already received
2017-12-09 12:47:21.211953 Peer sent entire transaction 28bd8ec0eeef7fcfc6ef95bbb13d5249eb2d6bcdef964815dd1f13534e36c152 that was already received
2017-12-09 12:47:24.414647 Peer sent entire transaction 55b649247f4f1c3401dff5ab149f1363821c6c26b39e0e9344b9e6c04b968277 that was already received
2017-12-09 12:47:25.638982 Peer sent entire transaction 55b649247f4f1c3401dff5ab149f1363821c6c26b39e0e9344b9e6c04b968277 that was already received
2017-12-09 12:47:25.852640 Peer sent entire transaction 55b649247f4f1c3401dff5ab149f1363821c6c26b39e0e9344b9e6c04b968277 that was already received
2017-12-09 12:47:31.968817 Peer sent entire transaction 91418671d582f9ca897299ecbada2a1b89048e84850fb8b449e36fb0cb64e0f3 that was already received
2017-12-09 12:47:32.112685 Peer sent entire transaction 91418671d582f9ca897299ecbada2a1b89048e84850fb8b449e36fb0cb64e0f3 that was already received
2017-12-09 12:47:35.474336 Peer sent entire transaction 91418671d582f9ca897299ecbada2a1b89048e84850fb8b449e36fb0cb64e0f3 that was already received
2017-12-09 12:47:36.768029 Peer sent entire transaction 4390d4b9df73c20f53e187f88f1d1a90bef6e58a9c4abf9fb0528b2287f56f88 that was already received
2017-12-09 12:47:40.935720 Peer sent entire transaction 958abe7a189bcc7669e8de0eec0895b11bcc21a4a74ad25380d55e7237baec5e that was already received
2017-12-09 12:47:41.006484 Peer sent entire transaction 958abe7a189bcc7669e8de0eec0895b11bcc21a4a74ad25380d55e7237baec5e that was already received
2017-12-09 12:47:41.180621 Peer sent entire transaction 958abe7a189bcc7669e8de0eec0895b11bcc21a4a74ad25380d55e7237baec5e that was already received
2017-12-09 12:47:42.799063 P2Pool: 18894 shares in chain (10338 verified/18895 total) Peers: 7 (1 incoming)
2017-12-09 12:47:42.799495  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2017-12-09 12:47:42.799797  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: (0.0000)=0.0000 BTC
2017-12-09 12:47:42.800125  Pool: 5909TH/s Stale rate: 4.8% Expected time to block: 13.4 days
2017-12-09 12:47:46.797353 Peer sent entire transaction 958abe7a189bcc7669e8de0eec0895b11bcc21a4a74ad25380d55e7237baec5e that was already received
2017-12-09 12:47:47.811957 Peer sent entire transaction 8ae74c9c3367fbbcf954e1f3dc085fa4dcca70dc075b016585fbf4d092327271 that was already received
2017-12-09 12:47:50.377209 Peer sent entire transaction 8ae74c9c3367fbbcf954e1f3dc085fa4dcca70dc075b016585fbf4d092327271 that was already received
2017-12-09 12:47:52.139107 Peer sent entire transaction 7906c45bfb1ac2d8cc68c1a112ec00f419f6c6f97d0dbdb9c472b680295f9916 that was already received
2017-12-09 12:47:55.676708 Generating a share with 1030867 bytes (796675 new) and 1749 transactions (1203 new)
2017-12-09 12:47:55.868625 New work for xxxxxxxxxxxxxxxxxxxxxxxxxx Diff: 331431.13 Share diff: 47521705.54 Block value: 14.40 BTC (1749 tx, 1031 kB)
2017-12-09 12:47:56.641314 Peer sent entire transaction ddc0747ebc82a8648afc7e25c820bd5a66cd624bf4dbf37a66ba9f2a1fce7444 that was already received
2017-12-09 12:47:56.650497 Peer sent entire transaction ddc0747ebc82a8648afc7e25c820bd5a66cd624bf4dbf37a66ba9f2a1fce7444 that was already received
2017-12-09 12:47:57.388120 Peer sent entire transaction 8ae74c9c3367fbbcf954e1f3dc085fa4dcca70dc075b016585fbf4d092327271 that was already received
2017-12-09 12:48:03.519249 Peer sent entire transaction 6ef6ca8a2e71117f951852a8054aaade92253bd3bf3edcd5c9540866aeb76875 that was already received
2017-12-09 12:48:03.780748 Peer sent entire transaction 3c23a8842d731c695162989c8aaeaaca8168a7829121c0136a405368d38e9c5b that was already received
2017-12-09 12:48:05.673745 Peer sent entire transaction 3c23a8842d731c695162989c8aaeaaca8168a7829121c0136a405368d38e9c5b that was already received
2017-12-09 12:48:11.758827 Peer sent entire transaction 3c23a8842d731c695162989c8aaeaaca8168a7829121c0136a405368d38e9c5b that was already received
2017-12-09 12:48:11.833870 Peer sent entire transaction 3c23a8842d731c695162989c8aaeaaca8168a7829121c0136a405368d38e9c5b that was already received
2017-12-09 12:48:12.804277 P2Pool: 18895 shares in chain (10339 verified/18896 total) Peers: 7 (1 incoming)
2017-12-09 12:48:12.804664  Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2017-12-09 12:48:12.804912  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: (0.0000)=0.0000 BTC
2017-12-09 12:48:12.805183  Pool: 6173TH/s Stale rate: 4.8% Expected time to block: 12.8 days
2017-12-09 12:48:13.162434 Peer sent entire transaction 3c23a8842d731c695162989c8aaeaaca8168a7829121c0136a405368d38e9c5b that was already received
2017-12-09 12:48:19.125554 Peer sent entire transaction e396580068983ef8e3ce328047b8beaa0c9b69a51a86c6df687e3b5519b8bafc that was already received
2017-12-09 12:48:19.265750 Peer sent entire transaction e396580068983ef8e3ce328047b8beaa0c9b69a51a86c6df687e3b5519b8bafc that was already received
2017-12-09 12:48:20.927594 Peer sent entire transaction e396580068983ef8e3ce328047b8beaa0c9b69a51a86c6df687e3b5519b8bafc that was already received

It keeps on doing that. I see that new work is send to the miners. Also the rest of the output makes me believe that the P2Pool node is running as it should.

The cgminer command I use to run cgminer and connect to p2pool is the following:
screen -d -m -S cgminer ~/git/vthoang/cgminer/cgminer -o stratum+tcp://127.0.0.1:9332 -u xxxxxxxxxxxxxxxxxxxxxxxxxxxx -p xxxxxxxxxxxxx --suggest-diff 32 --gekko-compac-freq 150 --gekko-2pac-freq 200

Can someone explain to me what i'm doing wrong?

Thank you

Extra info:
My setup is the following:
* Processor: i3 M350 @2.77Ghz (so it is not a powerful processor)
* RAM: 8GB
* OS: ubuntu server 16.04 LTS
* mining software: cgminer 4.10
* miners: a couple of gekkoscience compac and gekkoscience 2Pac

[bitlock1]

After mining for about 8 hours pypy is doing much better, was watching the cpu utilization and it never hit 100% like it did with python so I will watch this for awhile and it looks like the miners are generating shares

http://97.77.64.18:9332/static/index.html
The graphs page show a great decrease in latency  
The stats do show we create/solved a few solutions.

I still need to make sure I am using the correct branch.

I am seeing some of the same results as Cryptonomist....but assume my miners were too slow and the transaction was already complete.

logs with --bench

Code:

2017-12-09 06:58:49.092191 Peer sent entire transaction 899cbf82a1e839e565dc1bb6d6f7346760a17bfa0eb62ac52f426283a4c5c933 that was already received
2017-12-09 06:58:49.107110   15.113 ms for 0 txs in p2p.py:handle_remember_tx (15.113 ms/tx)
2017-12-09 06:58:49.739611    5.692 ms for work.py:got_response()
2017-12-09 06:58:49.757925    0.074 ms for 21 txs in handle_losing_tx (0.004 ms/tx)
2017-12-09 06:58:49.788240    7.113 ms for work.py:got_response()
2017-12-09 06:58:50.059477    5.123 ms for work.py:got_response()
2017-12-09 06:58:51.941826    9.247 ms for 35 txs in p2p.py:handle_remember_tx (0.264 ms/tx)
2017-12-09 06:58:52.559175    4.877 ms for work.py:got_response()
2017-12-09 06:58:52.710049    6.561 ms for work.py:got_response()
2017-12-09 06:58:54.069984    4.063 ms for work.py:got_response()
2017-12-09 06:58:54.758305    0.085 ms for 21 txs in handle_losing_tx (0.004 ms/tx)
2017-12-09 06:58:54.968584    4.851 ms for work.py:got_response()
2017-12-09 06:58:55.720537    6.651 ms for work.py:got_response()
2017-12-09 06:58:56.291616    0.084 ms for 20 txs in handle_losing_tx (0.004 ms/tx)
2017-12-09 06:58:56.377485    5.816 ms for work.py:got_response()
2017-12-09 06:58:56.494658    5.494 ms for work.py:got_response()
2017-12-09 06:58:57.356390    0.067 ms for 20 txs in handle_losing_tx (0.003 ms/tx)
2017-12-09 06:58:58.029431    0.084 ms for 34 txs in handle_losing_tx (0.002 ms/tx)
2017-12-09 06:58:58.076610    4.853 ms for work.py:got_response()
2017-12-09 06:58:58.155988   33.165 ms for update_remote_view_of_my_known_txs
2017-12-09 06:58:58.184428   27.724 ms for update_remote_view_of_my_known_txs
2017-12-09 06:58:58.211773   26.689 ms for update_remote_view_of_my_known_txs
2017-12-09 06:58:58.236410   24.039 ms for update_remote_view_of_my_known_txs
2017-12-09 06:58:58.258269   21.322 ms for update_remote_view_of_my_known_txs
2017-12-09 06:58:58.280302   21.479 ms for update_remote_view_of_my_known_txs
2017-12-09 06:58:58.302797   21.907 ms for update_remote_view_of_my_known_txs
2017-12-09 06:58:58.324515   21.185 ms for update_remote_view_of_my_known_txs
2017-12-09 06:58:58.342164   17.110 ms for update_remote_view_of_my_known_txs
2017-12-09 06:58:58.506453    2.884 ms for work.py:got_response()
2017-12-09 06:58:58.703789    3.334 ms for work.py:got_response()
2017-12-09 06:58:59.243816 Peer sent entire transaction 899cbf82a1e839e565dc1bb6d6f7346760a17bfa0eb62ac52f426283a4c5c933 that was already received
2017-12-09 06:58:59.275476   32.095 ms for 0 txs in p2p.py:handle_remember_tx (32.095 ms/tx)
2017-12-09 06:59:01.035604    4.068 ms for work.py:got_response()
2017-12-09 06:59:01.296439 Peer sent entire transaction 53e8f5decead09879430377a846cc5fa0248b8f20d997e3d7b021440577d6198 that was already received
2017-12-09 06:59:01.307575   11.334 ms for 0 txs in p2p.py:handle_remember_tx (11.334 ms/tx)
================
2017-12-09 07:15:59.335277    1.115 ms for 1 shares in sendShares (1.115 ms/share)
2017-12-09 07:15:59.336851    1.305 ms for 1 shares in sendShares (1.305 ms/share)
2017-12-09 07:15:59.338391    1.273 ms for 1 shares in sendShares (1.273 ms/share)
2017-12-09 07:15:59.513629 Generating a share with 1049203 bytes (4922 new) and 1682 transactions (14 new)
2017-12-09 07:15:59.742585 New work for 1P9NC51Xxxxxxxxxxxxxxxxxxxxxxx! Diff: 854.52 Share diff: 1597970.59 Block value: 17.53 BTC (1682 tx, 1049 kB)
2017-12-09 07:15:59.743501  404.192 ms for work.py:get_work()
2017-12-09 07:15:59.935287 Generating a share with 1049203 bytes (4922 new) and 1682 transactions (14 new)
2017-12-09 07:16:00.115778  370.224 ms for work.py:get_work()
2017-12-09 07:16:00.290388 Generating a share with 1049203 bytes (4922 new) and 1682 transactions (14 new)
2017-12-09 07:16:00.773628  655.698 ms for work.py:get_work()
2017-12-09 07:16:01.727765 Generating a share with 1049203 bytes (4922 new) and 1682 transactions (14 new)
2017-12-09 07:16:02.126340 1343.181 ms for work.py:get_work()
2017-12-09 07:16:02.414538 Generating a share with 1049203 bytes (4922 new) and 1682 transactions (14 new)
2017-12-09 07:16:02.663207  535.062 ms for work.py:get_work()
2017-12-09 07:16:02.966352 Generating a share with 1049203 bytes (4922 new) and 1682 transactions (14 new)
2017-12-09 07:16:03.127259  462.104 ms for work.py:get_work()
2017-12-09 07:16:03.128754 4236.527 ms for 1 shares in handle_shares (4236.527 ms/share)
2017-12-09 07:16:03.704863    0.060 ms for 0 txs in p2p.py:handle_remember_tx (0.060 ms/tx)
2017-12-09 07:16:04.041200    0.959 ms for 0 shares in sendShares (0.959 ms/share)

thanks  jtoomim

Moderator note: frodocooper edited this post to include code tags.

[jtoomim]

Are you still suggesting to run your 1mb_segwit branch?

Yes. http://github.com/jtoomim/p2pool master is currently just an old snapshot of http://github.com/p2pool/p2pool master. All of my new code is in 1mb_segwit. It looks like that's what you're running now, otherwise you wouldn't be getting the --bench output.

bitlock1, it looks like your node is sorta working now, but not very well. Your mining efficiency is only 73%. This is probably because of the slow CPU. When you're running p2pool with a slow CPU, it can take several seconds for your machine to download a new share from a peer, deserialize it, build a new share template, and send that share template to miners. In your case, it took 4.2 seconds to do the deserialization step, and up to 1.3 seconds to build a new share template. This means that your miners are hashing on an old share for at least 5.5 seconds out of every 30 seconds on average. That alone will reduce your expected revenue by about 18.3%. (There are also a few processing steps that aren't accounted for in my --bench output, which may be why you're seeing 27% in practice rather than 18.3%.)

However I experience some problems. Well actually I haven't been able to mine at all with jtoomim's fork. Somehow my miners don't mine.

Can you try mining on a different node on jtoomimnet to test to see if the problem is with your node or with your miners? You can use ml.toom.im:9332. If your node has publicly open ports, it might also be helpful if you PM me your IP address so I can take a look.

Cryptonomist, your CPU is faster than bitlock1's, and is probably fast enough to run jtoomimnet p2pool with pypy and with an acceptable (but not excellent) DOA+orphan rate, though of course faster would be better.

Edit: based on PMs, it looks like Cryptonomist's setup is working okay. jtoomimnet will often choose higher pseudoshare difficulty, especially on startup, and Cryptonomist is using USB miners with a very low hashrate (~80 GH/s), so he's only finding one stratum share (p2pool pseudoshare) every 15 minutes or so. But it's working.

[jtoomim]

I have a test node up mining Bitcoin Cash (using Bitcoin ABC) at http://woff.toom.im:9338/. I don't know if it can successfully mine blocks yet though.

[sawa]

I have a test node up mining Bitcoin Cash (using Bitcoin ABC) at http://woff.toom.im:9338/. I don't know if it can successfully mine blocks yet though.

Give me the source code, please, I will connect 2-3 nodes.
I have many miners who require a BCH node

[Minerdude8]

The closest node from me shows a very high latency, so I would like to set up a private noed for my 9 Antminer L3+s. I read here that the requirement is not that huge for Litecoin. Problem is that my internet speed is pretty low and I cannot improve it from 5mbit/1mbit(upload), is that a problem?

I got a Intel NUC NUC6CAYS Intel Celeron J3455 1.5 GHz, 2GB RAM, Windows 10. Can this run a node?