lightningnetwork / lnd

Lightning Network Daemon ⚡️
MIT License
7.69k stars 2.08k forks source link

[need help]: cpu load is high #7692

Closed kirito41dd closed 1 year ago

kirito41dd commented 1 year ago

Background

cpu load is always high, my mini host is very hot, is my config wrong?

Your environment

lnd.conf

bitcoin.active=1
bitcoin.node=bitcoind
bitcoin.mainnet=1
bitcoind.dir=/data00/bitcoin
bitcoind.rpcuser=lnd
bitcoind.rpcpass=**********
bitcoind.zmqpubrawtx=tcp://127.0.0.1:18502
bitcoind.zmqpubrawblock=tcp://127.0.0.1:18501
externalip=*****
externalhosts=*****
wallet-unlock-password-file=/data00/lnd/passwd

Steps to reproduce

Tell us how to reproduce this issue. Please provide stacktraces and links to code in question.

Expected behaviour

Tell us what should happen

Actual behaviour

图片

图片

{
    "version": "0.16.2-beta commit=v0.16.2-beta",
    "commit_hash": "fdbeb1e7023827f1cb499a81d474986aa569d945",
    "identity_pubkey": "037a592399*******79401d3ec717fb18cda",
    "alias": "037a5923990f7ddd1366",
    "color": "#3399ff",
    "num_pending_channels": 0,
    "num_active_channels": 0,
    "num_inactive_channels": 0,
    "num_peers": 1,
    "block_height": 789732,
    "block_hash": "000000000000000000044e347da9535fa7cd70f1d426cb00d7b6a9636475ea78",
    "best_header_timestamp": "1684083864",
    "synced_to_chain": true,
    "synced_to_graph": false,
    "testnet": false,
    "chains": [
        {
            "chain": "bitcoin",
            "network": "mainnet"
        }
    ],
    "uris": [
        "037a592*****9401d3ec717fb18cda@118.******:9735"
    ],
    "features": {
        "0": {
            "name": "data-loss-protect",
            "is_required": true,
            "is_known": true
        },
        "5": {
            "name": "upfront-shutdown-script",
            "is_required": false,
            "is_known": true
        },
        "7": {
            "name": "gossip-queries",
            "is_required": false,
            "is_known": true
        },
        "9": {
            "name": "tlv-onion",
            "is_required": false,
            "is_known": true
        },
        "12": {
            "name": "static-remote-key",
            "is_required": true,
            "is_known": true
        },
        "14": {
            "name": "payment-addr",
            "is_required": true,
            "is_known": true
        },
        "17": {
            "name": "multi-path-payments",
            "is_required": false,
            "is_known": true
        },
        "23": {
            "name": "anchors-zero-fee-htlc-tx",
            "is_required": false,
            "is_known": true
        },
        "27": {
            "name": "shutdown-any-segwit",
            "is_required": false,
            "is_known": true
        },
        "30": {
            "name": "amp",
            "is_required": true,
            "is_known": true
        },
        "31": {
            "name": "amp",
            "is_required": false,
            "is_known": true
        },
        "45": {
            "name": "explicit-commitment-type",
            "is_required": false,
            "is_known": true
        },
        "2023": {
            "name": "script-enforced-lease",
            "is_required": false,
            "is_known": true
        }
    },
    "require_htlc_interceptor": false,
    "store_final_htlc_resolutions": false
}
yyforyongyu commented 1 year ago

Closed as it's a duplication of #7675.

Could try to increase the bitcoind.txpollinginterval value first, and wait for the fix #7681 to be merged.