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.

Sign up for GitHub

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

Jump to bottom

Diagnose printf/scanf perf issues #48

Open
bushidocodes opened this issue Aug 2, 2021 · 0 comments
Open

Diagnose printf/scanf perf issues #48

bushidocodes opened this issue Aug 2, 2021 · 0 comments

Comments

@bushidocodes
Copy link
Contributor

Xiaosu noticed that printf and scanf functions seem to cause a substantial slowdown of modules running under Sledge. This might be due to LTO, it might be Sledge-backing specific, or it might be here.

image

The scope of this task is to compare the overhead of scanf and printf under wasmception, wasi-sdk, and native to determine if this is an issue here or downstream.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bushidocodes