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

u64 optimization #18

Open
mootz12 opened this issue Dec 24, 2024 · 0 comments
Open

u64 optimization #18

mootz12 opened this issue Dec 24, 2024 · 0 comments
Labels
optimization This issue deals with lowering resource usage

Comments

@mootz12
Copy link
Contributor

mootz12 commented Dec 24, 2024 •
edited
Loading

Explore if replacing u64 values with Timepoints or u32 where possible is worth it.

u64 requires the value be stored on the host, where Timepoints and u32 can be stored in the WASM VM.

This also requires 22.0.4 for upgraded benchmarking ability.
@mootz12 mootz12 added the optimization This issue deals with lowering resource usage label Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
optimization This issue deals with lowering resource usage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mootz12