-
Notifications
You must be signed in to change notification settings - Fork 4.6k
use staked connection for bench-tps in net scripts #34767
use staked connection for bench-tps in net scripts #34767
Conversation
clientCommand="\ | ||
solana-bench-tps \ | ||
--duration 7500 \ | ||
--sustained \ | ||
--threads $threadCount \ | ||
$benchTpsExtraArgs \ | ||
--read-client-keys ./client-accounts.yml \ | ||
--url "http://$entrypointIp:8899" \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case if we use staked connection, we need to specify rpc address even if ThinClient is employed. This address is used to create RpcClient to check stake of the specified address and later another RpcClient is created. So I believe that there is no harm in specifying it always
bdc6793
to
c9afb39
Compare
c9afb39
to
0411016
Compare
A side note, I tried TpuClient and ThinClient and the former outperforms the later always. Another observation is that TPS is very volatile now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Leaving it unapproved so that @apfitzge can review it as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Problem
After adding throttling to streamer bench-tps shows ~50tps. To fix this we use staked connection.
The same as #34749
Summary of Changes