From 6019f1bb0a0744ffa52bf1ab93309c1a6dd9063c Mon Sep 17 00:00:00 2001 From: Jason Carver Date: Tue, 26 May 2015 18:54:56 -0700 Subject: deep-mining-log: only track non-stale blocks if you track stale blocks, then you quickly overflow your ring buffer in the local network case where you're mining every block and generating a lot of stales. --- miner/worker.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'miner') diff --git a/miner/worker.go b/miner/worker.go index 6f618d632..fac2e6568 100644 --- a/miner/worker.go +++ b/miner/worker.go @@ -248,12 +248,12 @@ func (self *worker) wait() { canonBlock := self.chain.GetBlockByNumber(block.NumberU64()) if canonBlock != nil && canonBlock.Hash() != block.Hash() { stale = "stale-" + } else { + self.current.localMinedBlocks = newLocalMinedBlock(block.Number().Uint64(), self.current.localMinedBlocks) } glog.V(logger.Info).Infof("🔨 Mined %sblock #%v (%x)", stale, block.Number(), block.Hash().Bytes()[:4]) - self.current.localMinedBlocks = newLocalMinedBlock(block.Number().Uint64(), self.current.localMinedBlocks) - jsonlogger.LogJson(&logger.EthMinerNewBlock{ BlockHash: block.Hash().Hex(), BlockNumber: block.Number(), -- cgit