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

Subo1977

sr. member

Activity: 344

Merit: 250

Flixxo - Watch, Share, Earn!

Quote from: gyverlb on May 19, 2013, 01:34:42 PM

I compiled the latest git version of bitcoind and with

Code:

mintxfee=0.01
minrelaytxfee=0.005

this is currently twice as fast as 0.8.1 with every settings I tried (from ~6s bitcoind latency to ~3s).

I think These Settings Must be in satoshis for the latest git

K1773R

legendary

Activity: 1792

Merit: 1008

/dev/null

3s lag? holy shit!

gyverlb

hero member

Activity: 896

Merit: 1000

I compiled the latest git version of bitcoind and with

Code:

mintxfee=0.01
minrelaytxfee=0.005

this is currently twice as fast as 0.8.1 with every settings I tried (from ~6s bitcoind latency to ~3s).

Richy_T

legendary

Activity: 2576

Merit: 2267

1RichyTrEwPYjZSeAYxeiFBNnKC9UjC5k

Quote from: powersync on May 19, 2013, 11:52:47 AM

Can anyone point me in the right direction on how to update bitcoind from 8.1 to 8.2 from command line on a ubuntu 11.10 server with a tar file. I have it extracted and I run "make -f makefile.unix bitcoind". It builds the files and I run it but it still shows 8.1 when I do a getinfo. Any help would be great.

PS

are you running it from the install directory? You may need to do a 'make install' to make it the system default.

powersync

member

Activity: 77

Merit: 10

Can anyone point me in the right direction on how to update bitcoind from 8.1 to 8.2 from command line on a ubuntu 11.10 server with a tar file. I have it extracted and I run "make -f makefile.unix bitcoind". It builds the files and I run it but it still shows 8.1 when I do a getinfo. Any help would be great.

PS

furball

full member

Activity: 172

Merit: 100

Quote from: daemondazz on May 19, 2013, 06:28:53 AM

So I'm wondering whether the current long round time is related to the high latency issue. I've clicked on over a dozen of the servers in the list at http://p2pool-nodes.info/ and every single one of them has had a getwork template latency of >10 seconds.

I'm currently running a reindex on my bitcoind. It found a heap of orphan transactions and is now re-downloading the blockchain from around height 100,000...

I think I'm also going to have to temporarily switch to a different pool, until this catches up.

Could be right...I upgraded to the latest bitcoin version and applied the changes to the config per Prattlers suggestion and latency went away completely. What exactly do you mean by "catches up"? Will everybody need to update their bitcoind etc?

gyverlb

hero member

Activity: 896

Merit: 1000

Quote from: GrapeApe on May 19, 2013, 08:28:13 AM

I made some changes in the source code and compiled my own bitcoin-qt as per some controversial suggestions several weeks ago. My latency has been around 3.5 ms but about once an hour I get a spike as high as 2 seconds and that spike has caused a few orphans. What switch over are you speaking of on 5/15?

On 2013/5/5 block size in 0.8.1 nodes are allowed to be >500000 bytes and <0.8.0 versions must be upgraded to avoid remaining behind IIRC.

GrapeApe

sr. member

Activity: 476

Merit: 250

I made some changes in the source code and compiled my own bitcoin-qt as per some controversial suggestions several weeks ago. My latency has been around 3.5 ms but about once an hour I get a spike as high as 2 seconds and that spike has caused a few orphans. What switch over are you speaking of on 5/15?

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: daemondazz on May 19, 2013, 06:28:53 AM

So I'm wondering whether the current long round time is related to the high latency issue. I've clicked on over a dozen of the servers in the list at http://p2pool-nodes.info/ and every single one of them has had a getwork template latency of >10 seconds.

I'm currently running a reindex on my bitcoind. It found a heap of orphan transactions and is now re-downloading the blockchain from around height 100,000...

I think I'm also going to have to temporarily switch to a different pool, until this catches up.

I was thinking it might be related to the recent switchover. 5/15 just happened.

Could also be bad luck.

M

daemondazz

sr. member

Activity: 448

Merit: 250

So I'm wondering whether the current long round time is related to the high latency issue. I've clicked on over a dozen of the servers in the list at http://p2pool-nodes.info/ and every single one of them has had a getwork template latency of >10 seconds.

I'm currently running a reindex on my bitcoind. It found a heap of orphan transactions and is now re-downloading the blockchain from around height 100,000...

I think I'm also going to have to temporarily switch to a different pool, until this catches up.

gyverlb

hero member

Activity: 896

Merit: 1000

Quote from: zvs on May 19, 2013, 01:49:13 AM

i guess 'mintxfee' would be the creation tx fee, which you probably wont want to change unless you want to increase fees on your own transactions. i assume most pools run with the default setting of 0.0001

minrelaytxfee doesn't exist in 0.8.1 (it's a constant). Looking at the source (main.cpp, CTxMemPool::accept), I added:

Code:

limitfreerelay=0

to my configuration. It may not be enough (I've not fully grasped all the conditions where this is applied).

KALRONG

newbie

Activity: 52

Merit: 0

Quote from: Amph on May 19, 2013, 02:58:48 AM

yeah, two days and still no transactions, even with 4 share and efficiency of 130...
i switch to btcguild for now

remenber that the shares expire around 24h after you get them hehe

Amph

legendary

Activity: 3248

Merit: 1070

yeah, two days and still no transactions, even with 4 share and efficiency of 130...
i switch to btcguild for now

azw409

member

Activity: 73

Merit: 10

This current round is taking a long time :-(

daemondazz

sr. member

Activity: 448

Merit: 250

Quote from: mdude77 on May 18, 2013, 07:18:27 PM

I'm at 1s latency now. It was about 8-10 hours ago that I restarted it. Must behave differently on linux than it does windows. Or it's hardware related? What horsepower do you have under the hood? using an i7 on an SSD with 12gb of ram here.

I'm running on a HP Blade, quad core Xeon on SAS drives, so computing power shouldn't be an issue

Not sure what else to try...

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

blockminsize=0
blockprioritysize=0
blockmaxsize=5000 (you could reduce this to probably 2000 or 3000 and still pick up the odd super high transaction fee transfer. *1200 or below will always miss it, as it'll just have the 1 transaction from block)
minrelaytxfee=0.0005 (i assume that one works, i make the change in the source, which would be nMinRelayTxFee = 50000)

the post about increasing the relay fees = higher latency is wrong

ofc, if all blocks came from p2pool then we'd have issues if everyone had ^^^ those settings

i guess 'mintxfee' would be the creation tx fee, which you probably wont want to change unless you want to increase fees on your own transactions. i assume most pools run with the default setting of 0.0001

last edit, i think;

set maxblocksize to 1000. if you still have latency issues, then the issue lies somewhere other than with bitcoind and p2pool

gyverlb

hero member

Activity: 896

Merit: 1000

Here's the settings I'm currently trying (too soon to be sure it works).
This removes any room reserved for high priority transaction (using old inputs).

Code:

blockminsize=0
blockprioritysize=0
mintxfee=0.001

mintxfee might have to be raised to avoid the current set of problematic transactions (I'm not sure how much they paid by kB).

TurdHurdur

full member

Activity: 216

Merit: 100

Quote from: daemondazz on May 18, 2013, 07:14:48 PM

None of the above changes have made any difference for my node - I'm currently running at 11s Get Work latency. With a 10s block time, I can't help but think I'm never going to actually solve a share.

Restarting bitcoind drops the latency back down, but it climbs back up to >10s in about half hour. I'm now restarting once per hour from cron to attempt to get some period where I might be able to get some valid work.

This is with version 0.8.1-precise2 from http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu.

Any other ideas?

Code:

mintxfee=20000

...in bitcoin.conf worked pretty good for me, still get some fee'd transactions in and latency is under .1 seconds.

Edit: it ceased being effective, unfortunate...

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: daemondazz on May 18, 2013, 07:14:48 PM

None of the above changes have made any difference for my node - I'm currently running at 11s Get Work latency. With a 10s block time, I can't help but think I'm never going to actually solve a share.

Restarting bitcoind drops the latency back down, but it climbs back up to >10s in about half hour. I'm now restarting once per hour from cron to attempt to get some period where I might be able to get some valid work.

This is with version 0.8.1-precise2 from http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu.

Any other ideas?

I'm at 1s latency now. It was about 8-10 hours ago that I restarted it. Must behave differently on linux than it does windows. Or it's hardware related? What horsepower do you have under the hood? using an i7 on an SSD with 12gb of ram here.

M

daemondazz

sr. member

Activity: 448

Merit: 250

None of the above changes have made any difference for my node - I'm currently running at 11s Get Work latency. With a 10s block time, I can't help but think I'm never going to actually solve a share.

Restarting bitcoind drops the latency back down, but it climbs back up to >10s in about half hour. I'm now restarting once per hour from cron to attempt to get some period where I might be able to get some valid work.

This is with version 0.8.1-precise2 from http://ppa.launchpad.net/bitcoin/bitcoin/ubuntu.

Any other ideas?

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 544. (Read 2591920 times)