ironfish icon indicating copy to clipboard operation
ironfish copied to clipboard

Very long latency in mining

Open terrancewong opened this issue 2 years ago • 4 comments

What happened?

For miner/newBlocksStream, node gives out a new work for next block very long time after a new block synced. could be 10-80sec or even longer, under very low (< 2) system load.

Version

0.1.34

Debug output

No response

Relevant log output

No response

Graffiti

bh9sqoCqIR3rDFstCCCw1g

terrancewong avatar May 16 '22 05:05 terrancewong

0.1.36 still suffers from this issue. please look into it! latency goes up to 100+ seconds, rendering the node totally useless for mining.

terrancewong avatar Jun 17 '22 06:06 terrancewong

Are you still seeing this behavior?

lwisne avatar Aug 03 '22 23:08 lwisne

Yes. this issue still not solved, v0.1.41 and the latency becomes longer and longer, into hundreds of seconds. the node is useless for mining.

to verify this. start a miner/newBlocksStream, wait for new works, check last blcok timestamp.

for a in 1 ; do echo -n '{"type":"message","data":{"mid":1,"type":"miner/blockTemplateStream"}}\x0c' ; sleep 1 ; done | nc <node IP> <rpc port> | tr '\014' '\n'

might need --no-rpc.tcp.tls to see clear text block template

terrancewong avatar Aug 05 '22 03:08 terrancewong

Can also compare node status with newBlocksStream side by side, mining work comes much later than new block on the node.

terrancewong avatar Aug 05 '22 03:08 terrancewong

Closing due to staleness. If the issue persists in versions 1.0.0+ - please file a new issue

holahula avatar Apr 20 '23 22:04 holahula