You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently conducting performance testing on reth-bsc(reth: v1.5.1). After enabling parallel sparse trie, we have observed a significant reduction in validation time, from 120ms to <40ms.
To better understand the performance, we have added some metrics to measure the overall time spent for block insertion as well as the time spent in each phase (execution and validation). However, we are experiencing noticeable latency jitter in the overall time, as illustrated in the attached graph.
I would like to understand the reasons behind this jitter and seek advice on how to mitigate it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, reth team.
We are currently conducting performance testing on reth-bsc(reth: v1.5.1). After enabling parallel sparse trie, we have observed a significant reduction in validation time, from 120ms to <40ms.
To better understand the performance, we have added some metrics to measure the overall time spent for block insertion as well as the time spent in each phase (execution and validation). However, we are experiencing noticeable latency jitter in the overall time, as illustrated in the attached graph.
I would like to understand the reasons behind this jitter and seek advice on how to mitigate it.
Thank you for your assistance!
Beta Was this translation helpful? Give feedback.
All reactions