Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

πŸ› οΈ [TASK] : WASM Module benchmark #79

Closed
Tracked by #64
Mr-Leshiy opened this issue Feb 2, 2024 · 1 comment Β· Fixed by #109
Closed
Tracked by #64

πŸ› οΈ [TASK] : WASM Module benchmark #79

Mr-Leshiy opened this issue Feb 2, 2024 · 1 comment Β· Fixed by #109
Assignees

Comments

@Mr-Leshiy
Copy link
Contributor

Summary

Implement a benchmark for the Module::call_func function.

Description

Write a benchmark for Module::call_func to measure how long it takes to call a wasm function taking into account that during each execution a clean wasm state is initialised (which could be costly).

@Mr-Leshiy Mr-Leshiy self-assigned this Feb 2, 2024
@Mr-Leshiy Mr-Leshiy moved this to πŸ— In progress in Catalyst Feb 2, 2024
@stevenj
Copy link
Collaborator

stevenj commented Feb 5, 2024

Make sure we benchmark this with the wasi bindings PR merged, as it will be a better indication of the overhead in creating wasm instances.

@Mr-Leshiy Mr-Leshiy moved this from πŸ— In progress to πŸ‘€ In review in Catalyst Feb 14, 2024
@Mr-Leshiy Mr-Leshiy moved this from πŸ‘€ In review to πŸ— In progress in Catalyst Feb 22, 2024
@Mr-Leshiy Mr-Leshiy moved this from πŸ— In progress to πŸ‘€ In review in Catalyst Feb 27, 2024
@github-project-automation github-project-automation bot moved this from πŸ‘€ In review to βœ… Done in Catalyst Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants