i am having problems compiling for use with litecoin i keep receiving the following error any help???
C:\p2pool\litecoin_scrypt>C:\Python27\python.exe setup.py build --compile=mingw3
2 install
running build
running build_ext
building 'ltc_scrypt' extension
creating build
creating build\temp.win32-2.7
creating build\temp.win32-2.7\Release
gcc -mno-cygwin -mdll -O -Wall -I. -IC:\Python27\include -IC:\Python27\PC -c scr
yptmodule.c -o build\temp.win32-2.7\Release\scryptmodule.o
error: command 'gcc' failed: No such file or directory
Windows 7 64bit all the recommended packages were installed
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 634. (Read 2591920 times)
October 23, 2012, 09:11:18 PM
October 23, 2012, 12:59:15 PM
I agree it is mostly measuring bitcoin performance. With the new p2pool version some transaction data is now being distributed with p2pool and so that might lessen the load on bitcoind and make it return faster? We'll see I guess when it is fully switched over to 0.8. That is good news about the latest bitcoin.. I'll try the release candidates when they start coming out.
Your metric seems to measure the performance of bitcoin, not p2pool. Could it be that bitcoind is lagging more and more from the ever increasing load?
I have tried the latest experimental "ultraprune" bitcoin (git head) for about a day now, and have seen my stale rate go from 6-8% down to 3-4%. I have no nifty metrics other than what p2pool provides out of the box, though.
I've seen some evidence of this as well.. although I'm not 100% sure I'm logging the correct metric. I log the time for the getwork function in main.py and the delay is often in the 1-2 second range now whereas before it was often under 0.5 secs:
Your metric seems to measure the performance of bitcoin, not p2pool. Could it be that bitcoind is lagging more and more from the ever increasing load?
I have tried the latest experimental "ultraprune" bitcoin (git head) for about a day now, and have seen my stale rate go from 6-8% down to 3-4%. I have no nifty metrics other than what p2pool provides out of the box, though.
October 23, 2012, 11:58:07 AM
I've seen some evidence of this as well.. although I'm not 100% sure I'm logging the correct metric. I log the time for the getwork function in main.py and the delay is often in the 1-2 second range now whereas before it was often under 0.5 secs:
Your metric seems to measure the performance of bitcoin, not p2pool. Could it be that bitcoind is lagging more and more from the ever increasing load?
I have tried the latest experimental "ultraprune" bitcoin (git head) for about a day now, and have seen my stale rate go from 6-8% down to 3-4%. I have no nifty metrics other than what p2pool provides out of the box, though.
October 23, 2012, 09:24:13 AM
I've seen some evidence of this as well.. although I'm not 100% sure I'm logging the correct metric. I log the time for the getwork function in main.py and the delay is often in the 1-2 second range now whereas before it was often under 0.5 secs:
# BITCOIND WORK
bitcoind_work = variable.Variable((yield getwork(bitcoind)))
@defer.inlineCallbacks
def work_poller():
while True:
flag = factory.new_block.get_deferred()
try:
my_time = time.time()
bitcoind_work.set((yield getwork(bitcoind, bitcoind_work.value['use_getblocktemplate'])))
my_time2 = time.time() - my_time
if (my_time2 > 0.5):
print "slow bitcoind: %.02f" % (my_time2,)
There are some possible optimizations for the new transaction handling, which could be causing this by introducing some new latency. I'll look into it over the next few days.
# BITCOIND WORK
bitcoind_work = variable.Variable((yield getwork(bitcoind)))
@defer.inlineCallbacks
def work_poller():
while True:
flag = factory.new_block.get_deferred()
try:
my_time = time.time()
bitcoind_work.set((yield getwork(bitcoind, bitcoind_work.value['use_getblocktemplate'])))
my_time2 = time.time() - my_time
if (my_time2 > 0.5):
print "slow bitcoind: %.02f" % (my_time2,)
Also, my miner is also getting a rather high reject rate. I haven't changed my miner settings at all and I'm running the latest bitcoind and p2pool. My reject used to be <3% and now its ~6%
There are some possible optimizations for the new transaction handling, which could be causing this by introducing some new latency. I'll look into it over the next few days.
October 23, 2012, 06:32:10 AM
i hope this bad luck round is over soon 
We got no less than 6 blocks two days ago. That's about 3x as many as we should at our hashrate. I'm not complaining about a slow period!!
M
October 23, 2012, 05:25:40 AM
i hope this bad luck round is over soon
We got no less than 6 blocks two days ago. That's about 3x as many as we should at our hashrate. I'm not complaining about a slow period!!
M
October 23, 2012, 01:23:24 AM
i hope this bad luck round is over soon
EDIT: nvm there was a solved block some time ago
EDIT2: is there a bug? its not showing u p at the P2Pool stats (talking about the "Blocks found in last day:" section) :S
altough i have recieved the transaction. im talking about this one: http://blockexplorer.com/block/0000000000000305d32daae3ad63cd020b1fa75de9faf567284077b82a60b019
EDIT3: same for this block! http://blockexplorer.com/block/0000000000000307bb161f68458201e85a2004d9ec193ca548b004c68d678125
"Note that blocks may have been orphaned from the P2Pool chain and so not be here."EDIT: nvm there was a solved block some time ago
EDIT2: is there a bug? its not showing u p at the P2Pool stats (talking about the "Blocks found in last day:" section) :S
altough i have recieved the transaction. im talking about this one: http://blockexplorer.com/block/0000000000000305d32daae3ad63cd020b1fa75de9faf567284077b82a60b019
EDIT3: same for this block! http://blockexplorer.com/block/0000000000000307bb161f68458201e85a2004d9ec193ca548b004c68d678125
Some blocks are found by orphaned/doa shares
October 23, 2012, 01:18:02 AM
i hope this bad luck round is over soon
EDIT: nvm there was a solved block some time ago
EDIT2: is there a bug? its not showing u p at the P2Pool stats (talking about the "Blocks found in last day:" section) :S
altough i have recieved the transaction. im talking about this one: http://blockexplorer.com/block/0000000000000305d32daae3ad63cd020b1fa75de9faf567284077b82a60b019
EDIT3: same for this block! http://blockexplorer.com/block/0000000000000307bb161f68458201e85a2004d9ec193ca548b004c68d678125
"Note that blocks may have been orphaned from the P2Pool chain and so not be here."EDIT: nvm there was a solved block some time ago
EDIT2: is there a bug? its not showing u p at the P2Pool stats (talking about the "Blocks found in last day:" section) :S
altough i have recieved the transaction. im talking about this one: http://blockexplorer.com/block/0000000000000305d32daae3ad63cd020b1fa75de9faf567284077b82a60b019
EDIT3: same for this block! http://blockexplorer.com/block/0000000000000307bb161f68458201e85a2004d9ec193ca548b004c68d678125
Some blocks are found by orphaned/doa shares
October 22, 2012, 11:42:50 PM
i hope this bad luck round is over soon
EDIT: nvm there was a solved block some time ago
EDIT2: is there a bug? its not showing u p at the P2Pool stats (talking about the "Blocks found in last day:" section) :S
altough i have recieved the transaction. im talking about this one: http://blockexplorer.com/block/0000000000000305d32daae3ad63cd020b1fa75de9faf567284077b82a60b019
EDIT3: same for this block! http://blockexplorer.com/block/0000000000000307bb161f68458201e85a2004d9ec193ca548b004c68d678125
EDIT: nvm there was a solved block some time ago
EDIT2: is there a bug? its not showing u p at the P2Pool stats (talking about the "Blocks found in last day:" section) :S
altough i have recieved the transaction. im talking about this one: http://blockexplorer.com/block/0000000000000305d32daae3ad63cd020b1fa75de9faf567284077b82a60b019
EDIT3: same for this block! http://blockexplorer.com/block/0000000000000307bb161f68458201e85a2004d9ec193ca548b004c68d678125
October 22, 2012, 11:20:30 PM
Does the 8.2version support litecoin network?
I try to run p2pool 8.2v in LTC network, it will not show poolspeed, and cpu-miner will not work.
Try 5.0v, it promptes to upgrade.
I try to run p2pool 8.2v in LTC network, it will not show poolspeed, and cpu-miner will not work.
Try 5.0v, it promptes to upgrade.
I am running it on litecoin network...
BTC http://fearmypenguin.ath.cx:9332
LTC http://fearmypenguin.ath.cx:9327
not mining it right now but was last night.
Naelr
October 22, 2012, 10:45:15 PM
Does the 8.2version support litecoin network?
I try to run p2pool 8.2v in LTC network, it will not show poolspeed, and cpu-miner will not work.
Try 5.0v, it promptes to upgrade.
I try to run p2pool 8.2v in LTC network, it will not show poolspeed, and cpu-miner will not work.
Try 5.0v, it promptes to upgrade.
October 22, 2012, 07:03:50 PM
Hey, I set up a 0%-fee p2pool node on a Windows Azure VPS: 168.63.105.0:9332 - http://168.63.105.0:9332/static/
October 22, 2012, 05:58:47 PM
is there a neat way to look at the curent sharechain?
In meaning? You can look at stats page. October 22, 2012, 05:06:11 PM
is there a neat way to look at the curent sharechain?
In meaning? You can look at stats page. October 22, 2012, 04:57:39 PM
is there a neat way to look at the curent sharechain?
In meaning? You can look at stats page. October 22, 2012, 04:18:36 PM
is there a neat way to look at the curent sharechain?
October 22, 2012, 04:08:46 PM
Thank you forrestv! Sounds like a great feature for p2pool
Now to just get everyone to upgrade...
at 42% right now.
M
October 22, 2012, 03:09:09 PM
Thank you forrestv! Sounds like a great feature for p2pool
October 22, 2012, 02:51:51 PM
I just saw this message "transaction rescued from peer latency cache". Can someone explain what it means? Is it some new function in v8?
Yes, that message is a result of a new feature in v8:
* Transaction preforwarding Transactions that you're mining are sent to peers before you get a share, so any block solution you find can be broadcast virtually instantaneously. This could theoretically get our invalid block rate below any other pool's thanks to our large network of nodes.
P2Pool nodes indicate to their peers which transactions they have in memory so that peers don't need to send the full transaction when, for example, they produce a share containing that transaction. This is to reduce latency below what would result from using something like Bitcoin's "inv"/"getdata" messages, where sending a peer a transaction it doesn't yet know about takes three round-trips instead of one.
"Transaction rescued from peer latency cache" means that your node had a transaction in its memory, determined that it was no longer necessary to retain it, and forgot about it. Meanwhile, a peer is trying to forward the transaction to you and sees that you already have it, so it sends only the transaction hash instead of the full transaction. Were it not for the first node buffering the transaction for a few seconds before truly forgetting about it, sending the transaction hash instead of the full transaction would result in the first node not knowing about the transaction.
October 22, 2012, 02:33:26 PM
I just saw this message "transaction rescued from peer latency cache". Can someone explain what it means? Is it some new function in v8?
Jump to: