Skip to content

Add Configurable Variable Fuel Costs for Runtime-Sized Wasm Operations #13931

Description

@d-sonuga

Summary

OperatorCost only configures a flat cost for each Wasm operator.
Operations like memory.fill can do variable work and priced with a fixed 1 fuel per byte.
Add configurable per byte/unit costs to OperatorCost for embedders to have control over how the pricing is
done for these kind of instructions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementwasmtime:apiRelated to the API of the `wasmtime` crate itself

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions