Struct MemoryWeights

pub struct MemoryWeights {
    pub lazy_pages_signal_read: Weight,
    pub lazy_pages_signal_write: Weight,
    pub lazy_pages_signal_write_after_read: Weight,
    pub lazy_pages_host_func_read: Weight,
    pub lazy_pages_host_func_write: Weight,
    pub lazy_pages_host_func_write_after_read: Weight,
    pub load_page_data: Weight,
    pub upload_page_data: Weight,
    pub mem_grow: Weight,
    pub mem_grow_per_page: Weight,
    pub parachain_read_heuristic: Weight,
}

Describes the weight for memory interaction.

Each weight with lazy_pages_ prefix includes weight for storage read, because for each first page access we need to at least check whether page exists in storage. But they do not include cost for loading page data from storage into program memory. This weight is taken in account separately, when loading occurs.

Lazy-pages write accesses does not include cost for uploading page data to storage, because uploading happens after execution, so benchmarks do not include this cost. But they include cost for processing changed page data in runtime.

Fields

lazy_pages_signal_read: Weight

Cost per one [GearPage] signal read processing in lazy-pages,

lazy_pages_signal_write: Weight

Cost per one [GearPage] signal write processing in lazy-pages,

lazy_pages_signal_write_after_read: Weight

Cost per one [GearPage] signal write after read processing in lazy-pages,

lazy_pages_host_func_read: Weight

Cost per one [GearPage] host func read access processing in lazy-pages,

lazy_pages_host_func_write: Weight

Cost per one [GearPage] host func write access processing in lazy-pages,

lazy_pages_host_func_write_after_read: Weight

Cost per one [GearPage] host func write after read access processing in lazy-pages,

load_page_data: Weight

Cost per one [GearPage] data loading from storage and moving it in program memory. Does not include cost for storage read, because it is taken in account separately.

upload_page_data: Weight

Cost per one [GearPage] uploading data to storage. Does not include cost for processing changed page data in runtime, cause it is taken in account separately.

mem_grow: Weight

Cost per one [WasmPage] for memory growing.

mem_grow_per_page: Weight

Cost per one [WasmPage] for memory growing.

parachain_read_heuristic: Weight

Cost per one [GearPage]. When we read page data from storage in para-chain, then it should be sent to relay-chain, in order to use it for process queue execution. So, reading from storage cause additional resources consumption after block(s) production on para-chain.

Trait Implementations

impl Clone for MemoryWeights

fn clone(&self) -> MemoryWeights

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for MemoryWeights

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for MemoryWeights

fn default() -> Self

Returns the “default value” for a type.

impl From<MemoryWeights> for LazyPagesCosts

fn from(val: MemoryWeights) -> Self

Converts to this type from the input type.