[Proposal] Evaluate Arrow IPC format for reader
Open
Nobody has claimed this yet.
enhancement
Future
- Dominant language
- Python
- Stars
- 203
- Forks
- 67
- Avg merge
- 20m
- Merged PRs (30d)
- 8
Description
This issue tracks the proposal of evaluating Apache Arrow IPC as an alternative on‑disk data representation format for the MLPerf Storage reader pipeline, with the goal of improving effective data loading reducing CPU overhead during sample deserialization.
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 MLPerf Storage reader pipeline and its current sample-deserialization path. Evaluate Apache Arrow IPC as an alternative on-disk representation and compare its effect on CPU overhead during loading. The issue does not name files, tests, or acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100