influxdata / influxdata/datafusion-udf-wasm
Include HTTP Request+Response in DataFusion Memory Accounting
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 24
Description
# What
Include HTTP requests & responses (path + headers + body + footers) in DataFusion memory accounting.
# Why
These will be buffered in userspace and within the kernel, so we should limit them.
# How
Extend our existing memory pool integration to also cover the HTTP data.
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
Start by locating the existing memory pool integration and the HTTP request/response buffering paths. Trace how path, headers, body, and footers are allocated, then verify that tests cover their inclusion in memory accounting and that the configured limit applies to the combined usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100