spiccioli



Offline



Activity: 1377

Merit: 1000



nec sine labore







LegendaryActivity: 1377Merit: 1000nec sine labore Re: [400GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool November 12, 2012, 07:33:05 AM #3784



my 3.7 GH/s rig got two blocks in a few hours!!



Code:

2012-11-11 10:11:31.827311 GOT BLOCK FROM PEER! Passing to bitcoind! 10fec080 bitcoin: http://blockexplorer.com/block/000000000000017d6334ea4879445b3db2742aa4b126c15f780e359b10fec080

2012-11-11 18:05:00.046074 GOT BLOCK FROM MINER! Passing to bitcoind! http://blockexplorer.com/block/00000000000000e1a611799f954b950af31050e6d5faad27afba8a8678b57042

2012-11-11 18:05:00.107708 GOT BLOCK FROM PEER! Passing to bitcoind! 78b57042 bitcoin: http://blockexplorer.com/block/00000000000000e1a611799f954b950af31050e6d5faad27afba8a8678b57042

2012-11-11 22:03:58.762769 GOT BLOCK FROM PEER! Passing to bitcoind! 9d20b4e8 bitcoin: http://blockexplorer.com/block/000000000000006fa5a29ba508f2a7f6c4997f6698ce0be8935a72249d20b4e8

2012-11-11 23:05:28.105767 GOT BLOCK FROM PEER! Passing to bitcoind! c2e1a971 bitcoin: http://blockexplorer.com/block/000000000000027e355c4fd3ab9b31d37ea60744c5db52056245275bc2e1a971

2012-11-12 06:05:38.913612 GOT BLOCK FROM MINER! Passing to bitcoind! http://blockexplorer.com/block/000000000000013750ed9afc1288c6f1e27a9622aba80d03f744cb6f299d88b6









spiccioli OMG!my 3.7 GH/s rig got two blocks in a few hours!!spiccioli

spiccioli



Offline



Activity: 1377

Merit: 1000



nec sine labore







LegendaryActivity: 1377Merit: 1000nec sine labore Re: [400GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool November 12, 2012, 10:22:59 AM #3788 Quote from: cabin on November 09, 2012, 02:32:14 PM



Code: #Max number of nodes to connect to. Another possible bottleneck.

maxconnections=20



#Maximum size, in bytes, of blocks you create:

blockmaxsize=100000



#How many bytes of the block should be dedicated to high-priority transactions,

#included regardless of the fees they pay

blockprioritysize=2000



#Minimum block size you want to create; block will be filled with free transactions

#until there are no more or the block reaches this size:

blockminsize=0



#Fee-per-kilobyte amount (in BTC) considered the same as "free"

#Be careful setting this: if you set it to zero then

#a transaction spammer can cheaply fill blocks using

#1-satoshi-fee transactions. It should be set above the real

#cost to you of processing a transaction.

mintxfee=0.0005

You might want to try these settings in bitcoin.conf to improve your bitcoind performance if it is indeed the bottleneck. I've found processing hundreds of transactions can also slow things down so some of these settings limit the number of transactions to a couple hundred.

cabin



I think these options should be mandatory when running p2pool on a slow/old/single core pc and/or using an ADSL or any other kind of async/slow home transmission channel.



spiccioli.

cabinI think these options should be mandatory when running p2pool on a slow/old/single core pc and/or using an ADSL or any other kind of async/slow home transmission channel.spiccioli.

twmz



Offline



Activity: 737

Merit: 500









Hero MemberActivity: 737Merit: 500 Re: [400GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool November 12, 2012, 12:44:38 PM #3789

Since our current lucky streak has been completely jinxed already, I'll just pile on and point out that for the first time in nearly a year, the all-time luck is back to even!



Since our current lucky streak has been completely jinxed already, I'll just pile on and point out that for the first time in nearly a year, the all-time luck is back to even! TwmzX1wBxNF2qtAJRhdKmi2WyLZ5VHRs

WoT, GPG



Bitrated user: ewal. Was I helpful? 1X1wBxNF2qtAJRhdKmi2WyLZ5VHRsBitrated user: ewal.

cabin



Offline



Activity: 606

Merit: 250







Sr. MemberActivity: 606Merit: 250 Re: [400GH/s] p2pool: Decentralized, DoS-resistant, Hop-Proof pool November 12, 2012, 03:41:00 PM #3792 Quote from: spiccioli on November 12, 2012, 10:22:59 AM Quote from: cabin on November 09, 2012, 02:32:14 PM



Code: #Max number of nodes to connect to. Another possible bottleneck.

maxconnections=20



#Maximum size, in bytes, of blocks you create:

blockmaxsize=100000



#How many bytes of the block should be dedicated to high-priority transactions,

#included regardless of the fees they pay

blockprioritysize=2000



#Minimum block size you want to create; block will be filled with free transactions

#until there are no more or the block reaches this size:

blockminsize=0



#Fee-per-kilobyte amount (in BTC) considered the same as "free"

#Be careful setting this: if you set it to zero then

#a transaction spammer can cheaply fill blocks using

#1-satoshi-fee transactions. It should be set above the real

#cost to you of processing a transaction.

mintxfee=0.0005

You might want to try these settings in bitcoin.conf to improve your bitcoind performance if it is indeed the bottleneck. I've found processing hundreds of transactions can also slow things down so some of these settings limit the number of transactions to a couple hundred.

cabin



I think these options should be mandatory when running p2pool on a slow/old/single core pc and/or using an ADSL or any other kind of async/slow home transmission channel.



spiccioli.



cabinI think these options should be mandatory when running p2pool on a slow/old/single core pc and/or using an ADSL or any other kind of async/slow home transmission channel.spiccioli.

I don't think there is a way to enforce these, but we can certainly recommend them to everyone.. especially the transaction limit ones. I think I remember reading even the large pools were not letting their blocks grow massive in the hopes they propagate faster and have less orphans. I'm not sure if that was proven to be correct or not.. but it sounds plausible and I know in my personal case it reduced my getWork times. I don't think there is a way to enforce these, but we can certainly recommend them to everyone.. especially the transaction limit ones. I think I remember reading even the large pools were not letting their blocks grow massive in the hopes they propagate faster and have less orphans. I'm not sure if that was proven to be correct or not.. but it sounds plausible and I know in my personal case it reduced my getWork times.