Stream: git-wasmtime

Topic: wasmtime / issue #3080 Document the impact of the fields ...

Wasmtime GitHub notifications bot (Jul 13 2021 at 11:39):

tschneidereit opened issue #3080:

Wasmtime's ModuleLimits and InstanceLimits structs in config.rs can be used to tweak various limits imposed on modules/instances when using the pooling instance allocator. Unfortunately it's not easy to tell what the impact is of changing any of these limits. As an example, the limit on functions has a default of 10k; how bad is the impact of increasing that limit? Is it a relatively minor increase in module size, or a meaningful difference in instance size?

@peterhuene, do you think it's relatively straightforward to add a sentence or two on the impact of each of these?

Wasmtime GitHub notifications bot (Jul 13 2021 at 11:39):

tschneidereit labeled issue #3080:

Wasmtime's ModuleLimits and InstanceLimits structs in config.rs can be used to tweak various limits imposed on modules/instances when using the pooling instance allocator. Unfortunately it's not easy to tell what the impact is of changing any of these limits. As an example, the limit on functions has a default of 10k; how bad is the impact of increasing that limit? Is it a relatively minor increase in module size, or a meaningful difference in instance size?

@peterhuene, do you think it's relatively straightforward to add a sentence or two on the impact of each of these?

Wasmtime GitHub notifications bot (Jul 13 2021 at 11:39):

tschneidereit labeled issue #3080:

Wasmtime's ModuleLimits and InstanceLimits structs in config.rs can be used to tweak various limits imposed on modules/instances when using the pooling instance allocator. Unfortunately it's not easy to tell what the impact is of changing any of these limits. As an example, the limit on functions has a default of 10k; how bad is the impact of increasing that limit? Is it a relatively minor increase in module size, or a meaningful difference in instance size?

@peterhuene, do you think it's relatively straightforward to add a sentence or two on the impact of each of these?

Wasmtime GitHub notifications bot (Jul 13 2021 at 14:05):

peterhuene assigned issue #3080 (assigned to peterhuene):

Wasmtime's ModuleLimits and InstanceLimits structs in config.rs can be used to tweak various limits imposed on modules/instances when using the pooling instance allocator. Unfortunately it's not easy to tell what the impact is of changing any of these limits. As an example, the limit on functions has a default of 10k; how bad is the impact of increasing that limit? Is it a relatively minor increase in module size, or a meaningful difference in instance size?

@peterhuene, do you think it's relatively straightforward to add a sentence or two on the impact of each of these?

Wasmtime GitHub notifications bot (Jul 13 2021 at 14:06):

peterhuene commented on issue #3080:

Absolutely, I'll add more context as to what the cost is for increasing these values.

Wasmtime GitHub notifications bot (Jul 23 2021 at 23:46):

peterhuene closed issue #3080 (assigned to peterhuene):

Wasmtime's ModuleLimits and InstanceLimits structs in config.rs can be used to tweak various limits imposed on modules/instances when using the pooling instance allocator. Unfortunately it's not easy to tell what the impact is of changing any of these limits. As an example, the limit on functions has a default of 10k; how bad is the impact of increasing that limit? Is it a relatively minor increase in module size, or a meaningful difference in instance size?

@peterhuene, do you think it's relatively straightforward to add a sentence or two on the impact of each of these?

Last updated: Dec 23 2024 at 12:05 UTC