Closed congle-ibl closed 4 years ago
I'm having the same issue, please let me know if you find something. It's just terrible software. I could narrow it down to the number of peers, try to use only 1 or 2 peers at most, it might get better. Let me know the outcome please, still don't know what the problem is.
If you want to process all incoming transactions on EOS-Mainnet, please use EOSIO 2.0 with EOS-VM or a faster CPU (4.5GHz is probably needed for 1.8 WABT). The volume of transactions is quite high on EOS Mainnet and will only grow.
Additionally change read-mode option if you don't need speculative.
Are you using a fork of eosio? history-state-db-size-mb
is not a valid option in the eosio software provided by Block.one in this repository, and invalid config options should prevent eosio from starting.
I'm having the same issue, please let me know if you find something. It's just terrible software. I could narrow it down to the number of peers, try to use only 1 or 2 peers at most, it might get better. Let me know the outcome please, still don't know what the problem is.
8656
Meet the same issue, after about 1000 requests the response time up to 20s or more. Have to write a script to restart eos if met this situation. After restart, eos can response quickly in 20ms. However, after about another 1000 requests, the issue occurs again. Tried eos 1.8.4 and 1.8.9.
Resolved by https://github.com/EOSIO/eos/pull/8729
@allenhan2 please verify fix.
Related #8850
Resolved by #8894
Hi Team,
I'm running EOS fullnode with version 1.8.6. My node has synced successfully and up-to-date with latest block. But when calling /v1/chain/get_info, it takes a lot of time to response as below:
Here is my config.ini:
Please help to take a look, thank you in advance. Best Regards,