Closed weihaopeng closed 2 years ago
It's occasional.
Config:
{ "NODE_EVENTS": [ "tx", "bp", "block", "fork", "query" ], "W3_EVENTS": [ "network.msg.departure", "network.msg.arrival", "network.ready", "chain.block.added", "chain.fork", "node.verify" ], "NODES_AMOUNT": 5, "COLLECTORS_AMOUNT": 1, "WITNESSES_AMOUNT": 1, "WITNESS_ROUNDS_AMOUNT": 2, "INIT_CHAIN_INTERVAL": 10000, "MSG_ARRIVAL_RATIO": 1, "LATENCY_LOWER_BOUND": 0, "LATENCY_UPPER_BOUND": 100, "LOCAL_COMPUTATION_LATENCY": 30, "WITNESS_AND_MINT_LATENCY": 520, "UNCONFIRMED_BLOCKS_HEIGHT": 0, "EPOCH_TIME": 2210, "EPOCH_COLLECTING_TIME": 1690, "EPOCH_WITNESS_AND_MINT_TIME": 520, "SINGLE_NODE_MODE": false, "W3_EVENTS_ON": true, "tps": 15 }
tx_amount is 30.
need to destroy after execution.
This is what we expect exactly. Since the real last time of epoch is somewhat random rather than fixed.
It's occasional.
Config:
tx_amount is 30.