Graphene Stress Test Report

[kenCode]

That is the coolest grab I have ever seen. Sexy.

[btswolf]

impressive

@kenCode
That`s the screenshot

[wuyanren]

I think there should be enough time to test, for example, for 10 hours.

[clayop]

100 TPS / 23 min stress test result. Result: "Stable"

[bytemaster]

delegate.btsnow is out

Talking with him now.  His machine is running with a debug build on windows on a home internet connection with FULL logging on VM.

[bytemaster]

How long is it gonna run for? Just had to stop working on the GUI due to this because it's killing my witness_node... :(

1 hour... Sorry about that :(

Me too.   Stopping the test would be preferred at this point.

[clayop]

delegate.btsnow is out

[clayop]

How long is it gonna run for? Just had to stop working on the GUI due to this because it's killing my witness_node... :(

1 hour... Sorry about that :(

[svk]

How long is it gonna run for? Just had to stop working on the GUI due to this because it's killing my witness_node... :(

[clayop]

Looks very stable.

[clayop]

Stress test will begin at 10/9 19:00 UTC

[clayop]

100 TPS / 1 hour test will begin at 10/8 20:00 UTC

[clayop]

Flooding nodes are forked :'( I have to setup them again... I will notice the next test schedule soon.

[lakerta06]

100 TPS / 1 hour test will take place at 10/8 18:00 UTC (14:00 EST, 11:00 PST)

I always have a hard time converting to my local time, so if anybody has the same promblem here you go:
http://www.timeanddate.com/worldclock/fixedtime.html?month=10&day=8&year=2015&hour=18&min=0&sec=0

[clayop]

100 TPS / 1 hour test will take place at 10/8 18:00 UTC (14:00 EST, 11:00 PST)

[bytemaster]

Some inits seems to be forked.

Actually all of them.

This was not because of the flood, but due to a loss of internet connectivity in our office.   They recovered automatically (with no intervention on my part) when the internet came back up.   This is especially interesting because they produced a very long fork because all 10 were on one machine.   

[clayop]

It looks perfect  ;)

[jakub]

Some inits seems to be forked.

Actually all of them.

[clayop]

Some inits seems to be forked.

[clayop]

5 min... looks really awesome

[clayop]

60 TPS / 20 min test will begin at 21:25 UTC

[fuzzy]

If there was a way of preventing a witness node from sharing any blocks other than the block they just produced, I think we could reduce the network lag that seems to be the issue with higher tps.

Said another way.  If a witness node only had to worry about receiving transactions, receiving blocks, and broadcasting a block on there turn would it reduce the performance requirements enough to make it worth the changes?

Cool, other than  nodes doing  that, will make  them a prime targets for a ddos attack...

There are ways to mitigate DDoS attacks that I am certain the best and brightest will be utilizing now and inn coming years. :)

I definitely have mixed fillings on the term 'inn coming' :)
...especially when combined with 'the best'

damn your spell checker tony!  :'(

[tonyk]

If there was a way of preventing a witness node from sharing any blocks other than the block they just produced, I think we could reduce the network lag that seems to be the issue with higher tps.

Said another way.  If a witness node only had to worry about receiving transactions, receiving blocks, and broadcasting a block on there turn would it reduce the performance requirements enough to make it worth the changes?

Cool, other than  nodes doing  that, will make  them a prime targets for a ddos attack...

There are ways to mitigate DDoS attacks that I am certain the best and brightest will be utilizing now and inn coming years. :)

I definitely have mixed fillings on the term 'inn coming' :)
...especially when combined with 'the best'

[fuzzy]

If there was a way of preventing a witness node from sharing any blocks other than the block they just produced, I think we could reduce the network lag that seems to be the issue with higher tps.

Said another way.  If a witness node only had to worry about receiving transactions, receiving blocks, and broadcasting a block on there turn would it reduce the performance requirements enough to make it worth the changes?

Cool, other than  nodes doing  that, will make  them a prime targets for a ddos attack...

There are ways to mitigate DDoS attacks that I am certain the best and brightest will be utilizing now and inn coming years. :)

[tonyk]

If there was a way of preventing a witness node from sharing any blocks other than the block they just produced, I think we could reduce the network lag that seems to be the issue with higher tps.

Said another way.  If a witness node only had to worry about receiving transactions, receiving blocks, and broadcasting a block on there turn would it reduce the performance requirements enough to make it worth the changes?

Cool, other than  nodes doing  that, will make  them a prime targets for a ddos attack...

[puppies]

If there was a way of preventing a witness node from sharing any blocks other than the block they just produced, I think we could reduce the network lag that seems to be the issue with higher tps.

Said another way.  If a witness node only had to worry about receiving transactions, receiving blocks, and broadcasting a block on there turn would it reduce the performance requirements enough to make it worth the changes?

[clayop]

30 TPS / 1 hour test. Seems quite stable.

[clayop]

[clayop]

Next small test in 15 min (22:25 UTC). 30 TPS for 1 hour.

[xeroc]

+1

[sudo]

 8) that is awesome job +5% +5% +5% +5%

[Moon]

Nice Job ！  :D 

[spartako]

Great!  +5%

[clayop]

[cass]

I think web-wallet server should be upgraded  :P

:P yep block explorer extremly stucking currently ..

[clayop]

I think web-wallet server should be upgraded  :P

[clayop]

5 min elapse. NO witness is down (!) and around 70-130 TPS

[clayop]

1 minute left...

[clayop]

Warming up soon... for 1 min.

[clayop]

Sorry I made a mistake. The test will start in 50 min (22:10 UTC)

:'(

It was simple omission. I forgot input screen session names... :'(

[wuyanren]

Sorry I made a mistake. The test will start in 50 min (22:10 UTC)

:'(

[clayop]

Sorry I made a mistake. The test will start in 50 min (22:10 UTC)

[wuyanren]

eagerly waiting...

haha

[bytemaster]

eagerly waiting...

[wuyanren]

Are you starting the test now

[clayop]

Next stress test will take plact at 2015/10/5 21:00 UTC.

The goal is maintaining 100 tps on average for 30 min (Since I don't have enough CORE, I cannot run for 1 hour)

[xeroc]

impressive

[clayop]

Maximum: block 36375 : 3238.7 TPS

[clayop]

Here are screenshots

[clayop]

Did your spam kill the testnet network?

Good work!

Yeah  8) I will upload the screenshot soon

[cube]

Did your spam kill the testnet network?

Good work!

[clayop]

Next spamming will begin at 23:30 UTC today, for 10 minutes.

[clayop]

We made over 1000 TPS!!! (1132.7 tps)



26233 '1.6.8' 'init7' 1820
26232 '1.6.10' 'init9' 3398
26231 '1.6.13' 'betaxtrade' 483

26233 '1.6.8' 'init7' 1820 '2015-10-03T14:00:18'
26232 '1.6.10' 'init9' 3398 '2015-10-03T14:00:15'
26231 '1.6.13' 'betaxtrade' 483 '2015-10-03T14:00:12'

[clayop]

With five different account and vps, I made the biggest block with 3524 txs (391.6 tps)
https://graphene.bitshares.org/#/block/15655

My next goal is four times than this result, with 20 vps and 20 different account, 1000 tps.

[clayop]

Spamming will begin at 2015/10/3 00:30 UTC

VPSs will send about 1200 txs per second for 10 minutes

[clayop]

I will run preliminary spam test in 15 min (21:30 UTC)

[clayop]

I'm waiting for graphene ppa update and over 90% witness participation rate. Once the conditions meet, I will update a stress test plan.

[fuzzy]

thanks for updating.  this is good stuff :)

[clayop]

The 3rd test is postponed due to the network problem.

[sudo]

From the third stress test (spamming) I decided to post the report on a separate thread.

3rd Test Plan:
- Time: 2015/10/1 00:00 UTC
- Duration: 30 min
- Number of VPS Used: 67
- Parameter: Using Xeroc's python script. Interval 1, 10 txs (= 10 tps per each vps)
- Goal: 500 tps

cool test 
twitter facebook   gogogo

[clayop]

From the third stress test (spamming) I decided to post the report on a separate thread.

3rd Test Plan:
- Time: TBD
- Duration: 30 min
- Number of VPS Used: 67
- Parameter: Using Xeroc's python script. Interval 1, 10 txs (= 10 tps per each vps)
- Goal: 500 tps