-
Notifications
You must be signed in to change notification settings - Fork 861
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thread Blocked When Added Transaction #3373
Comments
I think there's a few things going on here. I would start with this:
|
Thank you for your answer. I think my smart contract uses more gas than the gas usage recorded in the log file. If I tune my block time to minimize round changes, Isn't the performance worse? And there is no problem with node resources, but only 1 tx is going in each block.
Even if transactions per second is lowered, the result is the same. Please suggest a specific solution. |
With blockperiodseconds=1 I would expect block times in the order of seconds not minutes. Can you try with blockperiodseconds of 2 or 3 (and also increase the requesttimeoutseconds as recommended)? Also recommend observing the behaviour of the IBFT2 block propose/import process with fewer transactions being fired. You can check the besu logs for IBFT2 round change messages. |
@SeongUkJeon I have seen a similar issue when the node is running in a machine with slow storage. Maybe this is the case? Could you confirm the specs of the hardware you are running this node on? |
@lucassaldanha I have enough storage and I'm using SSD |
I don't think it is related to the number of open files. I just wanted to eliminate the issue when running Besu in slow storage. |
@macfarla As you suggested, I tested by setting |
1000 expired transactions - I recommend observing the behaviour of the IBFT2 block propose/import process with fewer transactions being fired. You can check the besu logs for IBFT2 round change messages. |
@macfarla I tested by setting
|
#59 Block mining time is In conclusion, it took 25 minutes and 59 seconds from the start of the test to mining one block. |
These log messages |
So with 0 transactions being fired, you're getting blocks every 2s. And then you fire 400 tx at a rate of 75 per second and things slow down. What happens if you fire 5, 10 or 20 per second? Alternatively, what happens if you lower the block gas limit? |
hi @SeongUkJeon - we've been unable to reproduce so closing this one. If you've got more information or questions, please reopen. |
I sent 190 transactions per second to the Besu network.
If a transaction used 337,472 gas in the log, multiple transactions were stored in one block,
but a problem occurred when a transaction used 1,222,986 gas in the log.
Transactions are written to the block only if this is the case.
A block is created approximately every 3 minutes and 30 seconds, and only one transaction is recorded in the block.
If the Transaction Gas Limit is less than that value, the following exception occurs.
My ibftConfigFile is
My bootnode options are
My other nodes options are
Versions (Add all that apply)
cat /etc/*release
]uname -a
]Additional Information
The text was updated successfully, but these errors were encountered: