-
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
Performance issue #3487
Comments
Hi @SeongUkJeon, that's awesome, you found some interesting things with your testing. With IBFT2 and blockchain in general, a lot depends on your individual environment - network latency, hardware, etc. It looks like you've made some headway to finding the optimal tuning settings for your environment.
|
@macfarla As we continue to test, we will find the appropriate optimal value. Thanks once again. |
@macfarla What is the relationship between blockperiodseconds and block size? |
Glad you found the right value for you environment! If blockperiodseconds is too low, there isn't enough time for the validators to exchange the messages required to agree on the block. This depends mostly on network latency - how long does it take for the validators to exchange messages. |
@macfarla This is the test result requested by #3373.
Is this the limit of besu's performance?
I tested by setting
Transaction Gas Limit = 1,000,000,000
blockperiodseconds=2
requesttimeoutseconds=4
Result:
1.
start: 2022-02-22 14:23:46,373 INFO o.a.j.e.StandardJMeterEngine: Running the test!
end: 2022-02-22 15:48:39.605+09:00 | EthScheduler-Workers-3 | INFO | PersistBlockTask | Imported #161 / 109 tx / 0 om / 1,807,636,604 (0.0%) gas / (0x6a127fe785bbbe8bcfe536a6eead0f9523a1bd78f8e83ecdaba1ce15496c1ac7) in 1.222s. Peers: 3
start: 2022-02-22 16:13:26,675 INFO o.a.j.e.StandardJMeterEngine: Running the test!
end: 2022-02-23 02:03:07.732+09:00 | pool-8-thread-1 | INFO |
start: 2022-02-23 11:18:55,928 INFO o.a.j.e.StandardJMeterEngine: Running the test!
end: 2022-02-23 13:07:32.271+09:00 | pool-8-thread-1 | INFO |
The text was updated successfully, but these errors were encountered: