Graphene Stress Test Report

[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]