influxdata / influxdata/datafusion-udf-wasm
WASM Payload Bloat Check
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 24
Description
# What
Add a CI check that ensures our WASM payload doesn't grow too large.
# Why
Larger payloads are harder to JIT-compile.
# How
Target the "add one" Rust payload and Python payload. Compile both in release mode. Check their size.
A few tools that could be helpful:
- https://github.com/surma/wasmphobia
- https://github.com/google/bloaty
- https://github.com/AlexEne/twiggy
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the CI configuration and the "add one" Rust and Python payloads, then inspect how each is compiled in release mode. Compare the size-check options mentioned in the issue, and consider the work complete when CI builds both payloads and fails if either exceeds the agreed size limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust, wasm
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100