Worst case Wasm CPU soak test

[maxzaver]

Motivation

We are currently using this code https://github.com/nearprotocol/nearcore/blob/master/runtime/runtime-params-estimator/test-contract/src/lib.rs#L681 to compute the ratio <num CPU instructions>/<num Wasm operations>. However this code might not be pessimistic enough, it might not be emitting the worst case Wasm operations. This might lead us to underestimating the cost of Wasm operations which might open the potential abuse vector.

Goal

We need to write Wasm code that emits as many as possible CPU instructions per Wasm operation. It cannot use thread-specific stuff so atomics cannot be used.

[willemneal]

This seems like a good use case for a fuzzer.

[bowenwang1996]

@olonho what is the status of this issue?

[stale]

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

[bowenwang1996]

@matklad @olonho

[stale]

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.