Re: How (and why) to use the Relay Network - page 5.

CohibAA

full member

Activity: 223

Merit: 132

Quote from: Matt Corallo on August 24, 2015, 01:40:30 PM

So currently the relay network *really* cant handle the spam attacks, because of things that need changed in the way mining works in bitcoin - see https://github.com/TheBlueMatt/RelayNode/issues/12 and https://github.com/bitcoin/bitcoin/issues/6531. When the next spam attacks start, expect block compression to go from 1/2 packets quite often to 500k very quickly (see-also http://bitcoinrelaynetwork.org/stats.html, though without changes I'll have to just turn off compression completely because of bandwidth costs, probably).

Matt, I just wanted to thank you for your great work on this and other projects.

FWIW, my RelayNode has not had any problems during the last 24+ hours of increased transaction activity (and for a pretty long time before).

Matt Corallo

hero member

Activity: 755

Merit: 515

So currently the relay network *really* cant handle the spam attacks, because of things that need changed in the way mining works in bitcoin - see https://github.com/TheBlueMatt/RelayNode/issues/12 and https://github.com/bitcoin/bitcoin/issues/6531. When the next spam attacks start, expect block compression to go from 1/2 packets quite often to 500k very quickly (see-also http://bitcoinrelaynetwork.org/stats.html, though without changes I'll have to just turn off compression completely because of bandwidth costs, probably).

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Done

Matt Corallo

hero member

Activity: 755

Merit: 515

If people could update to at least include https://github.com/TheBlueMatt/RelayNode/commit/6c479374f1f7f9a9338b656f8d5baa45d91e7d2c in their build, it would help a lot...when people start spamming the network the b/w usage on the relay servers spikes to much higher than reasonable, which may cause most servers to use more b/w than their monthly allotment.

It has no effect on the effectiveness of the relay network, and is almost entirely redundant.

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: Matt Corallo on August 02, 2015, 03:41:43 PM

Strange that it prints garbage to start, but that does actually look like its working. Wait 30 seconds and see if it prints a bunch of messages about transactions received/sent?

And few seconds later windows halts the program.
The message in the dialog box means that windows have closed the program

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: amaclin on August 02, 2015, 03:21:59 PM

When I execute it with parameters it prints some garbage.
And few seconds later windows halts the program.
(Sorry, the Windows displays dialog box in Russian)

Strange that it prints garbage to start, but that does actually look like its working. Wait 30 seconds and see if it prints a bunch of messages about transactions received/sent?

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: Matt Corallo on August 02, 2015, 03:01:37 PM

Well, I told you I fixed your original bug :p. Sadly, I dont have any Windows boxes anywhere to test with, and it works in wine now....So you get not prints when you try to run it, and it also doesnt run when you specify your local bitcoind (ie "relaynetworkclient.exe my-bitcoind-address 8333")?

When I execute it with parameters it prints some garbage.
And few seconds later windows halts the program.
(Sorry, the Windows displays dialog box in Russian)

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: amaclin on August 01, 2015, 07:06:09 AM

Now it does not start at all Grin

Windows 7x64

What stable build can be used?

Well, I told you I fixed your original bug :p. Sadly, I dont have any Windows boxes anywhere to test with, and it works in wine now....So you get not prints when you try to run it, and it also doesnt run when you specify your local bitcoind (ie "relaynetworkclient.exe my-bitcoind-address 8333")?

amaclin

legendary

Activity: 1260

Merit: 1019

Quote from: Matt Corallo on July 31, 2015, 07:59:50 PM

Quote from: amaclin on July 31, 2015, 10:35:33 AM

WTF with latest executable?

Should be fixed now.

Now it does not start at all Grin

Windows 7x64

What stable build can be used?

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: amaclin on July 31, 2015, 10:35:33 AM

WTF with latest executable?

Should be fixed now.

loshia

legendary

Activity: 1610

Merit: 1000

Quote from: amaclin on July 31, 2015, 10:35:33 AM

WTF with latest executable?

Code:

D:\RelayNetwork>relaynetworkclient.exe
Assertion failed: connection.cpp:78

D:\RelayNetwork>relaynetworkclient.exe --help
UASsAsGeEr:t iDo:n\ failed: connection.cReplpa:y7N8e
two

Wtf dude M$ crap
.....

amaclin

legendary

Activity: 1260

Merit: 1019

WTF with latest executable?

Code:

D:\RelayNetwork>relaynetworkclient.exe
Assertion failed: connection.cpp:78

D:\RelayNetwork>relaynetworkclient.exe --help
UASsAsGeEr:t iDo:n\ failed: connection.cReplpa:y7N8e
two

Matt Corallo

hero member

Activity: 755

Merit: 515

In other news, things seem to be working pretty well now but I probably wont be able to devote a ton of time writing new features in the near future, and since I spent a ton of time recently refactoring the whole codebase, contributing should now be reasonably possible. I'm sure we could drop global relay times another 10-20% pretty easily, and put up some issues at https://github.com/TheBlueMatt/RelayNode/issues that should be reasonably doable for people without stepping on code everywhere else (well, except maybe the rething-low-level-transport-protocol one).

Matt Corallo

hero member

Activity: 755

Merit: 515

Quote from: kano on July 26, 2015, 05:23:44 PM

Question:
So if I see 'S' 66% sends and 'R' 34% receives in the data in my log, that would represent that I'm supplying ~50% of the transactions to the server I connect to?
... since each receive is followed by a send, 'S' 66% would be 100% of the transactions and 'R' 34% would be the amount of those transaction that were sent to me?
i.e. 100 - (R / S) would be my % ?

Ignore out-of-band transactions (it should be pretty much 1:1, then, which means you are, as expected, pretty much just echoing all the transactions the server sends you...see https://github.com/TheBlueMatt/RelayNode/issues/11). Out-of-band transactions are just you sending transactions that the relay network may or may not have already seen that probably arent going to be used to compress things (see https://github.com/TheBlueMatt/RelayNode/issues/13).

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Matt Corallo on July 24, 2015, 08:00:20 PM

Added a node in Siberia which improves Japan/Beijing<->EU times, though its not publicly available to connect to (if anyone is mining in Russia and wants to connect to it, please ping me). Check out the nice little map of where the nodes are now at the bottom of the stats page (http://bitcoinrelaynetwork.org/stats.html#hotspot_map)

Question:
So if I see 'S' 66% sends and 'R' 34% receives in the data in my log, that would represent that I'm supplying ~50% of the transactions to the server I connect to?
... since each receive is followed by a send, 'S' 66% would be 100% of the transactions and 'R' 34% would be the amount of those transaction that were sent to me?
i.e. 100 - (R / S) would be my % ?

squidicuz

newbie

Activity: 58

Merit: 0

Quote from: Matt Corallo on July 24, 2015, 08:00:20 PM

Check out the nice little map of where the nodes are now at the bottom of the stats page (http://bitcoinrelaynetwork.org/stats.html#hotspot_map)

Awesome! It is neat being able to see the network map.

Matt Corallo

hero member

Activity: 755

Merit: 515

Added a node in Siberia which improves Japan/Beijing<->EU times, though its not publicly available to connect to (if anyone is mining in Russia and wants to connect to it, please ping me). Check out the nice little map of where the nodes are now at the bottom of the stats page (http://bitcoinrelaynetwork.org/stats.html#hotspot_map)

loshia

legendary

Activity: 1610

Merit: 1000

Thanks Jonny,
That was exactly what I wanted to say from beginnig. But my English sucks Wink

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Exactly. I was asking him to investigate what he's got going on with his bitcoin daemon since the relay client doesn't connect to issue RPC commands over 8332, it connects as a peer over 8333. I was also letting him know that merge mining coins on p2pool doesn't impact his bitcoin daemon. It impacts his miners, and the pool is constantly sending restarts (resulting in higher discarded/rejected work) as new blocks are found on those alt coins.

In other words, changing the rpcthreads parameter should have no impact on the relay client. Now, if he's solo mining and has 100 miners pointed to that bitcoin daemon, each making requests to create blocks, then he'd want to increase the rpcthreads parameter.

Seeing all of those disconnects, I'd suggest looking at the maxconnections. Default is 125. If he's running up against that number, then the relay client connection could be rejected by the node. Then again, my node runs at 125 connections and the relay network doesn't suffer the disconnection problem he's reporting.

loshia

legendary

Activity: 1610

Merit: 1000

Jonny,
Relay client is like Bitcoin node peer for his btcd. It has nothing to do with RPC or how ovreloaded btc deamon was.
Max peer count is exhausted and that is all. All of us shall take care of it in one way or on other.

Topic: Re: How (and why) to use the Relay Network - page 5. (Read 695 times)