Zero copy data API
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 463
- PR merge metrics
- No merged PRs in 30d
Description
Let me just start with, we're not currently a user of uPlot, but we're evaluating various options.
Zero-copy is important to us because our system often returns 20MB+ data as Apache Arrow records, and expanding them to regular objects/arrays in JS is not workable, both from a latency perspective and memory (expanding them can easily yield 100MB+ data, which is also not something we want to burden clients with).
I'm not very familiar with uPlot's architecture, so I don't know if it's feasible to do something like this. That said, is there an appetite for a zero-copy data API? If so, what would it take to do this?
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named. Start by reviewing uPlot's existing data input API and the surrounding chart-data architecture, then assess how Apache Arrow records could be consumed without expanding them into regular JavaScript objects or arrays. Done means documenting feasibility, the required API scope, and any performance or compatibility constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100