[bisq-network/bisq] *High* CPU usage with local bitcoind (#3593)

Darosior notifications at github.com
Mon Dec 2 11:16:32 UTC 2019


Here are some logs, it seems to be continuously trying to connect:
```
Dec-02 12:08:16.240 [AbstractTimeoutHandler timeouts] INFO  o.b.c.PeerGroup: [127.0.1.1]:8333: Peer died      (0 connected, 0 pending, 1 max)
Dec-02 12:08:16.241 [PeerGroup Thread] INFO  o.b.c.PeerGroup: Peer discovery took 5.373 μs and returned 0 items
Dec-02 12:08:16.241 [PeerGroup Thread] INFO  o.b.c.PeerGroup: Waiting 114740 msec before next connect attempt to [127.0.0.1]:8333
Dec-02 12:08:50.064 [JavaFX Application Thread] INFO  b.n.p.p.PeerManager: Num of latestLivePeers=8
Dec-02 12:08:59.619 [JavaFX Application Thread] INFO  b.n.p.p.PeerManager: We have 11 connections open. Our limit is 12
Dec-02 12:10:10.981 [PeerGroup Thread] INFO  o.b.c.PeerGroup: Attempting connection to [127.0.0.1]:8333     (0 connected, 1 pending, 1 max)
Dec-02 12:10:10.982 [NioClientManager] INFO  o.b.n.NioClientManager: Connected to /127.0.0.1:8333
Dec-02 12:10:10.982 [NioClientManager] INFO  o.b.core.Peer: Announcing to /127.0.0.1:8333 as: /bitcoinj:0.14.7.bisq.1-SNAPSHOT/Bisq:1.2.3/
Dec-02 12:10:14.446 [JavaFX Application Thread] INFO  b.c.d.s.DaoStateService: New Block added at blockHeight 606298
Dec-02 12:10:14.447 [JavaFX Application Thread] INFO  b.c.d.n.p.BlockParser: Parsing 0 transactions at block height 606298 took 0 ms
Dec-02 12:10:14.447 [JavaFX Application Thread] INFO  b.c.d.s.DaoStateService: Parse block completed: Block height 606298, 0 BSQ transactions.
Dec-02 12:10:15.982 [AbstractTimeoutHandler timeouts] INFO  o.b.c.PeerSocketHandler: [127.0.0.1]:8333: Timed out
Dec-02 12:10:15.982 [AbstractTimeoutHandler timeouts] INFO  o.b.c.PeerGroup: [127.0.0.1]:8333: Peer died      (0 connected, 0 pending, 1 max)
Dec-02 12:10:15.982 [PeerGroup Thread] INFO  o.b.c.PeerGroup: Peer discovery took 7.079 μs and returned 0 items
Dec-02 12:10:15.982 [PeerGroup Thread] INFO  o.b.c.PeerGroup: Waiting 10004 msec before next connect attempt to [127.0.1.1]:8333
Dec-02 12:10:18.439 [JavaFX Application Thread] INFO  b.c.b.w.BsqWalletService: updateBsqBalance took 15 ms
Dec-02 12:10:25.987 [PeerGroup Thread] INFO  o.b.c.PeerGroup: Attempting connection to [127.0.1.1]:8333     (0 connected, 1 pending, 1 max)
Dec-02 12:10:25.987 [NioClientManager] INFO  o.b.n.NioClientManager: Connected to darosior/127.0.1.1:8333
Dec-02 12:10:25.987 [NioClientManager] INFO  o.b.core.Peer: Announcing to darosior/127.0.1.1:8333 as: /bitcoinj:0.14.7.bisq.1-SNAPSHOT/Bisq:1.2.3/
Dec-02 12:10:30.987 [AbstractTimeoutHandler timeouts] INFO  o.b.c.PeerSocketHandler: [127.0.1.1]:8333: Timed out
Dec-02 12:10:30.988 [AbstractTimeoutHandler timeouts] INFO  o.b.c.PeerGroup: [127.0.1.1]:8333: Peer died      (0 connected, 0 pending, 1 max)
```

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/3593#issuecomment-560351921
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191202/e8416ba4/attachment.html>


More information about the bisq-github mailing list