facebookresearch / facebookresearch/dlrm

how to inference ./dlrm_s_criteo_kaggle.sh

Open
#361 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
4.1k
Forks
859
PR merge metrics
No merged PRs in 30d

Description

Hello

I recently read your DLRM paper and decided to try running the code myself. However, I'm a silly teenager who finds this field quite challenging.

I've tried training the model using this command ./bench/dlrm_s_criteo_kaggle.sh --test-freq=1024 and tweaked the values of the Criteo Kaggle dataset to train in various ways. What I'm really curious about is inference.

  1. Does using ./bench/dlrm_s_criteo_kaggle.sh --inference-only execute the inference process simply? (I don't think so, based on the git issues you've responded to in the past. It seems like the model needs to be saved first. Is that correct?)

  2. In the case where --data-generation = dataset what does the input data set structure look like during inference? (Does the original Criteo Kaggle dataset and a dataset where I've manually modified some values have the same input data?)

Thank you.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with bench/dlrm_s_criteo_kaggle.sh and inspect how --inference-only and --data-generation=dataset are handled. Document whether a saved model is required and what input structure inference expects, including how modified Criteo data relates to the original dataset.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, shell
Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.