-
Notifications
You must be signed in to change notification settings - Fork 622
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
Metric: number of fungible token transfers #10885
Comments
Comment from @staffik
|
"perf" method is useful only to replay latest txs on chain so it is useless here. |
@Longarithm , how would adversenet set up look like? something like these?
|
Yeah, except that we had only one node. Actually setup with N nodes / N shards also must add strong value by checking how much bandwidth is lost due to network and sharding. |
We had 1 validator node and 1 RPC node. |
I think what I would like to know is this. What is LoE to do do the following?
Is it still 2 weeks? Or more since it's somewhat more complicated than what Alex mentioned? |
For this benchmark, let's have at least 5 validators per shard (so 30 total) to make it closer to real-world scenario without making the benchmark too expensive to run |
@marcelo-gonzalez 's comment
|
@MCJOHN974 is looking into this measuring this metric to a first approximation using https://github.com/near/nearcore/blob/master/pytest/tests/loadtest/locust/README.md |
I've created a tracking issue for the MVP of this benchmark: #11348 |
We now publish the metric for number of FT transfers to this dashboard: https://grafana.nearone.org/d/fdo204e4y88owa/continuous-benchmarks?orgId=1 |
The setup for the FT benchmark is described in https://docs.nearone.org/doc/crt-benchmark-8IpRzRV7C5 |
Set up infrastructure to periodically run a throughput test to see how many fungible token transfers a fork of mainnet can do. This assumes that there is a fungible token contract deployed on every shard. cc @walnut-the-cat
The text was updated successfully, but these errors were encountered: