Test Net for Advanced Users

[puppies]

I was seeing average latency times around 1500ms on all three of my nodes during the spam test this morning.  I usually see around 100-300. 

[sittingduck]

Only an issue during spamming


Sent from my iPhone using Tapatalk

[clayop]

I suspect what is happening is the other peers are forgetting about the inventory notification and it is never being rebroadcast so it sits in the local node's cache until it expires.

Is it problematic or natural?

[spartako]

Can it be an issue or considered just as node performance problem?

Actually I don't know whats going on, if the wallet has problem to broadcast or it try and the transactions are refused by peers...

Meanwile new record: 225.6 tx/sec!:

https://graphene.bitshares.org/#/block/197175

I was able to do it launching 10 cli_wallet pointing to a single witness and flooding 10 tx per block each cli_wallet

[bytemaster]

http://127.0.0.1:8080/#/block/197175  had 660 transactions which is enough to choke the web GUI :) 

Don't try to load that block.

[bytemaster]

I suspect what is happening is the other peers are forgetting about the inventory notification and it is never being rebroadcast so it sits in the local node's cache until it expires.

[clayop]

155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

Thanks your help spamming with me!  +5%

Btw, my spamming performance is too low; about 10 tps only. Because of I'm using virtual machine in my laptop? is there any tips for well-performed spamming?

I don't know why, probably depend on power of machine, I'm on digital ocean with 16G, 8 core (anyway is a virtual machine).
What I see if I try to push too many transaction I see that transactions are not broadcasted so I start a command like this

Code Select Expand


node bin/flood.js spartako spartako1 ws://127.0.0.1:8099 400


But after 1000/1200 tx I kill the program (C-c) and usually I have spikes similar when I obtained 155 tps.

If I continue to spam at this rate it seems that transactions are not broadcasted.
The balance goes down and after a while goes up, example:

Code Select Expand


list_account_balances spartako
725729.97991 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
718831.99894 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
715724.23278 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
710737.10803 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
705602.99434 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
724512.07155 CORE



Can it be an issue or considered just as node performance problem?

[Xeldal]

witness 'xeldal' is updated to master

[spartako]

155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

Thanks your help spamming with me!  +5%

Btw, my spamming performance is too low; about 10 tps only. Because of I'm using virtual machine in my laptop? is there any tips for well-performed spamming?

I don't know why, probably depend on power of machine, I'm on digital ocean with 16G, 8 core (anyway is a virtual machine).
What I see if I try to push too many transaction I see that transactions are not broadcasted so I start a command like this

Code Select Expand


node bin/flood.js spartako spartako1 ws://127.0.0.1:8099 400


But after 1000/1200 tx I kill the program (C-c) and usually I have spikes similar when I obtained 155 tps.

If I continue to spam at this rate it seems that transactions are not broadcasted.
The balance goes down and after a while goes up, example:

Code Select Expand


list_account_balances spartako
725729.97991 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
718831.99894 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
715724.23278 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
710737.10803 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
705602.99434 CORE

unlocked >>> list_account_balances spartako
list_account_balances spartako
724512.07155 CORE



[clayop]

155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

Thanks your help spamming with me!  +5%

Btw, my spamming performance is too low; about 10 tps only. Because of I'm using virtual machine in my laptop? is there any tips for well-performed spamming?

[spartako]

155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

Thanks your help spamming with me!  +5%

[clayop]

155 tps! Good job spartako.

https://graphene.bitshares.org/#/block/187317

[bytemaster]

Is it best practice to git install ntp on the witness node, or does Graphene have a built in time syncing protocol?

It is best practice to have NTP or PTP installed... to get to 1 second blocks we will need PTP installed on all witness nodes using a single source.

what if this source get screwed/manipulated in future?

There are more complex algorithms that do not depend upon a central source that would use a phase-locked loop.   An example of how this could work:

1. Each machine is assumed broadcast their blocks at multiples of the block interval (1 second)
2. Each machine receives blocks from the other machine with some random latency added on to the time signal.
3. The receiver "KNOWS" the blocks were sent 1 second apart even if they were received .95 or 1.05 seconds apart.
4. The receiver can used this input stream to find the time that minimizes the error for all of the samples.
5. The receiver can then adjust his own clock (slowly) to get closer to his estimate of the sender's clock

So long as the adjustments made are very small relative to the noise in the signal, then both parties can lock to each other at the same time.  Under this system the two machines may drift from real time, but they will drift together and maintain an average of 1 second blocks.

[liondani]

Is it best practice to git install ntp on the witness node, or does Graphene have a built in time syncing protocol?

It is best practice to have NTP or PTP installed... to get to 1 second blocks we will need PTP installed on all witness nodes using a single source.

what if this source get screwed/manipulated in future?

[betax]

so that is the step missing !

Code Select Expand

import_key "delegate.ihashfury" "wif_priv_keywif_priv_keywif_priv_keywif_priv_key" true