Skip to content

YAML config support for pipeline benchmarking #3180

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

SSYernar
Copy link
Contributor

Summary:
Added a support for YAML file configuration of the pipeline benchmarking. This feature makes easier to reproduce complex configurations without the need to CLI arguments passing.

Example .yaml file should look like:

RunOptions:
  world_size: 2

PipelineConfig:
  pipeline: "sparse"

Also, configs can be listed in a 'flat' way as well:

world_size: 2
pipeline: "sparse"

To run, add the --yaml_config flag with the .yaml file path. Additional flags can overwrite the yaml file configs as well if desired.

Differential Revision: D78127340

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 10, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D78127340

SSYernar added a commit to SSYernar/torchrec that referenced this pull request Jul 11, 2025
Summary:

Added a support for YAML file configuration of the pipeline benchmarking. This feature makes easier to reproduce complex configurations without the need to CLI arguments passing.

Example `.yaml ` file should look like:
```
RunOptions:
  world_size: 2

PipelineConfig:
  pipeline: "sparse"
```

Also, configs can be listed in a 'flat' way as well:
```
world_size: 2
pipeline: "sparse"
```

To run, add the `--yaml_config` flag with the `.yaml` file path. Additional flags can overwrite the `yaml` file configs as well if desired.

Differential Revision: D78127340
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D78127340

SSYernar added a commit to SSYernar/torchrec that referenced this pull request Jul 11, 2025
Summary:
Pull Request resolved: pytorch#3180

Added a support for YAML file configuration of the pipeline benchmarking. This feature makes easier to reproduce complex configurations without the need to CLI arguments passing.

Example `.yaml ` file should look like:
```
RunOptions:
  world_size: 2

PipelineConfig:
  pipeline: "sparse"
```

Also, configs can be listed in a 'flat' way as well:
```
world_size: 2
pipeline: "sparse"
```

To run, add the `--yaml_config` flag with the `.yaml` file path. Additional flags can overwrite the `yaml` file configs as well if desired.

Differential Revision: D78127340
@SSYernar SSYernar force-pushed the export-D78127340 branch 2 times, most recently from 7ee0623 to 46f0bde Compare July 14, 2025 17:28
SSYernar added a commit to SSYernar/torchrec that referenced this pull request Jul 14, 2025
Summary:

Added a support for YAML file configuration of the pipeline benchmarking. This feature makes easier to reproduce complex configurations without the need to CLI arguments passing.

Example `.yaml ` file should look like:
```
RunOptions:
  world_size: 2

PipelineConfig:
  pipeline: "sparse"
```

Also, configs can be listed in a 'flat' way as well:
```
world_size: 2
pipeline: "sparse"
```

To run, add the `--yaml_config` flag with the `.yaml` file path. Additional flags can overwrite the `yaml` file configs as well if desired.

Differential Revision: D78127340
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D78127340

SSYernar added a commit to SSYernar/torchrec that referenced this pull request Jul 14, 2025
Summary:
Pull Request resolved: pytorch#3180

Added a support for YAML file configuration of the pipeline benchmarking. This feature makes easier to reproduce complex configurations without the need to CLI arguments passing.

Example `.yaml ` file should look like:
```
RunOptions:
  world_size: 2

PipelineConfig:
  pipeline: "sparse"
```

Also, configs can be listed in a 'flat' way as well:
```
world_size: 2
pipeline: "sparse"
```

To run, add the `--yaml_config` flag with the `.yaml` file path. Additional flags can overwrite the `yaml` file configs as well if desired.

Differential Revision: D78127340
SSYernar added a commit to SSYernar/torchrec that referenced this pull request Jul 15, 2025
Summary:

Added a support for YAML file configuration of the pipeline benchmarking. This feature makes easier to reproduce complex configurations without the need to CLI arguments passing.

Example `.yaml ` file should look like:
```
RunOptions:
  world_size: 2

PipelineConfig:
  pipeline: "sparse"
```

Also, configs can be listed in a 'flat' way as well:
```
world_size: 2
pipeline: "sparse"
```

To run, add the `--yaml_config` flag with the `.yaml` file path. Additional flags can overwrite the `yaml` file configs as well if desired.

Differential Revision: D78127340
Summary:
Pull Request resolved: pytorch#3180

Added a support for YAML file configuration of the pipeline benchmarking. This feature makes easier to reproduce complex configurations without the need to CLI arguments passing.

Example `.yaml ` file should look like:
```
RunOptions:
  world_size: 2

PipelineConfig:
  pipeline: "sparse"
```

Also, configs can be listed in a 'flat' way as well:
```
world_size: 2
pipeline: "sparse"
```

To run, add the `--yaml_config` flag with the `.yaml` file path. Additional flags can overwrite the `yaml` file configs as well if desired.

Differential Revision: D78127340
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D78127340

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants