Degraded performance of node’s RPC estimatesmartfee after upgrade to V27.1 #30555

1. 
   arshad-deriv commented at 8:18 am on July 31, 2024: none

   Is there an existing issue for this?

   • I have searched the existing issues

   Current behaviour

   I have recently upgraded Bitcoin node from v26.0 to v27.1. I have noticed that RPC calls being Time Out specifically for estimatesmartfee reaching 120 seconds.

   Expected behaviour

   If possible, RPC calls like estimatesmartfee should return the response faster.

   Steps to reproduce

   Not all the time the mentioned RPC call timeout but there are a few cases after our upgrade to v27.1.

   Relevant log output

   There is not much in Bitcoin logs that I analyzed.

   How did you obtain Bitcoin Core

   Compiled from source

   What version of Bitcoin Core are you using?

   bitcoin-v27.1-x86_64-linux-gnu

   Operating system and version

   linux

   Machine specifications

   I am using the

   • Linux OS
   • m5.xlarge aws instance Default config for
   • Wallet type is still legacy.
   • rpcclienttimeout = 900 sec
   • rpcservertimeout = 30 sec
   • dbcache = 450
   • v2transport = true
2. 
   maflcko commented at 8:43 am on July 31, 2024: member

   There is not much in Bitcoin logs that I analyzed.

   It would be easier to debug if there were some debug logs. Specifically, -debug=rpc -debug=http -debug=bench may be interesting.

   (This will fill your debug log faster, so make sure to disable it again, after you obtained the logs)

3. maflcko added the label Linux/Unix on Jul 31, 2024
4. maflcko added the label TX fees and policy on Jul 31, 2024
5. maflcko added the label RPC/REST/ZMQ on Jul 31, 2024
6. maflcko added the label Resource usage on Jul 31, 2024
7. maflcko added the label Questions and Help on Jul 31, 2024
8. 
   willcl-ark commented at 11:15 am on August 1, 2024: member

   Yes we will need some logs to debug this further, I see estimatesmartfee running extremely quickly on 27.1, so there is likely something else at play here:

    0$ /usr/bin/time -v bitcoin-cli estimatesmartfee 6 economical
    1{
    2  "feerate": 0.00003446,
    3  "blocks": 6
    4}
    5        Command being timed: "bitcoin-cli estimatesmartfee 6 economical"
    6        User time (seconds): 0.00
    7        System time (seconds): 0.00
    8        Percent of CPU this job got: 100%
    9        Elapsed (wall clock) time (h:mm:ss or m:ss): 0:00.00
   10        Average shared text size (kbytes): 0
   11        Average unshared data size (kbytes): 0
   12        Average stack size (kbytes): 0
   13        Average total size (kbytes): 0
   14        Maximum resident set size (kbytes): 4736
   15        Average resident set size (kbytes): 0
   16        Major (requiring I/O) page faults: 0
   17        Minor (reclaiming a frame) page faults: 182
   18        Voluntary context switches: 2
   19        Involuntary context switches: 0
   20        Swaps: 0
   21        File system inputs: 0
   22        File system outputs: 0
   23        Socket messages sent: 0
   24        Socket messages received: 0
   25        Signals delivered: 0
   26        Page size (bytes): 4096
   27        Exit status: 0
   

9. 
   maflcko commented at 8:30 am on August 5, 2024: member

   • m5.xlarge aws instance Default config for

   • Wallet type is still legacy.

   Which type of AWS storage are you using? What is the size of the wallet?

10. maflcko added the label Wallet on Aug 5, 2024
11. 
    maflcko commented at 10:57 am on August 7, 2024: member

    Closing for now, but please add any more details below (or in a new issue), if you have them, or if someone else runs into the same problem and has more details.
12. maflcko closed this on Aug 7, 2024

    ---

13. bitcoin locked this on Aug 7, 2025

Contributors
arshad-deriv maflcko willcl-ark

Labels
Wallet Linux/Unix TX fees and policy RPC/REST/ZMQ Resource usage Questions and Help