NVIDIA-Merlin / NVIDIA-Merlin/Transformers4Rec
[FEA] Sparse input
Open
Nobody has claimed this yet.
status/needs-triage
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 165
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
Is there a way for the library to handle very large sparse input,
something with ?
item_id: # 50 millions.
session_id : 50 millions
Usually, Rec are sparse data problem, so handling sparse data would be best.
Thanks
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
The issue names no file, test, or entry point; start by locating the library's input handling for item_id and session_id. Clarify the sparse representation and scale requirements, then define acceptance tests showing 50-million-value inputs can be handled without dense expansion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100