Andrew Borg (Kashin)

In https://github.com/near/nearcore/pull/8805, we introduce `compute_usage` field in `ExecutionOutcome`. Ideally, it would be treated similarly to `gas_burnt` field for consistency, but that requires more work due to two reasons: - `ExecutionOutcome`...

With the introduction of [Compute Costs](https://github.com/near/NEPs/blob/master/neps/nep-0455.md) the chunk now also has a **Compute Limit** beside the usual **Gas Limit**. At the moment Compute Limit matches the Gas Limit. This introduces...

This is a part of investigation for changing gas costs for function calls: https://github.com/near/nearcore/issues/10829 We need to: - [ ] Modify the `action_function_call` and `wasm_contract_loading_bytes` - [ ] Build a...

Investigate the effects of decreasing function call gas/compute cost

6

This issue tracks the implications of decreasing the [`action_function_call`](https://github.com/near/nearcore/blob/7cb90878b2c18cdea9453ddcaf78bc9e212baeb5/core/parameters/res/runtime_configs/parameters.snap#L41) costs from 4.6TGas (send + execution) to 700GGas. This work is a part of https://github.com/near/near-one-project-tracking/issues/59. UPD: To avoid undercharging, the plan...

Support Compute Costs for Actions

1

At the moment we only support [Compute Costs](https://github.com/near/NEPs/blob/master/neps/nep-0455.md) for host functions (https://github.com/near/nearcore/pull/8426) which had a higher priority for Flat Storage deployment. This is a tracking bug for work on supporting...

Investigate relationship between state size and performance on FT benchmark

1

We know that contract state size influences performance of the chain because it affects the latency of smart contract operations interacting with the disk. It is especially noticeable on shards...

[Tracking issue] Measure performance improvements of stateless validation on FT benchmark

2

We now have the [FT benchmark](https://github.com/near/nearcore/issues/11348) that measures max number of FT transfers that single NEAR shard can handle. We want to evaluate performance improvements brought by stateless validation on...

Investigate high memory and disk usage for FT benchmark

2

In the [FT benchmark](https://github.com/near/nearcore/issues/11348), on a powerful machine we were able to increase the gas limit to 10 PGas and increase the throughput to 3000 TPS. However, at this load,...

Introduce a way to change capacity of the network on the fly in FT benchmark

4

At the moment we can only easily change the capacity of the network at the startup time by increasing the `gas_limit`. For the FT throughput experiment, we want to find...

Run FT benchmark with multiple nodes

1

We want to repeat FT benchmark with a larger network, at least 5 nodes and check whether the throughput for the experiment with larger gas limit stays roughly the same.