Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Prototype benchmarking with private/custom devices that are not leased via AWS #8251

Open
guangy10 opened this issue Feb 6, 2025 · 0 comments
Open

Prototype benchmarking with private/custom devices that are not leased via AWS #8251

guangy10 opened this issue Feb 6, 2025 · 0 comments
Assignees
@huydhn
Labels
feature A request for a proper, new feature. module: benchmark Issues related to the benchmark infrastructure module: user experience Issues related to reducing friction for users triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Comments

@guangy10
Copy link
Contributor

guangy10 commented Feb 6, 2025 •
edited by pytorch-bot bot
Loading

🚀 The feature, motivation and pitch

In some scenarios, users may want to use private/custom devices for benchmarking.

  • The device is not available via AWS, e.g. old phones, embedded systems, etc.
  • For confidential reason, can't run in the public device pool, e.g. FoA/RL models, etc.

This task is to experiment whether we can support this feature within OSS benchmark infra.

CC: @kimishpatel @digantdesai @cbilgin

Alternatives

No response

Additional context

No response

RFC (Optional)

No response

cc @huydhn @kirklandsign @shoumikhin @mergennachin @byjlw
@guangy10 guangy10 added feature A request for a proper, new feature. module: benchmark Issues related to the benchmark infrastructure module: user experience Issues related to reducing friction for users labels Feb 6, 2025
@digantdesai digantdesai added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Feb 6, 2025
@mergennachin mergennachin moved this from To triage to Backlog in ExecuTorch DevX improvements Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@huydhn huydhn

Labels
feature A request for a proper, new feature. module: benchmark Issues related to the benchmark infrastructure module: user experience Issues related to reducing friction for users triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
ExecuTorch DevX improvements
Status: Backlog
PyTorch OSS Dev Infra
Status: No status
Milestone
No milestone
Development

No branches or pull requests
3 participants
@digantdesai @huydhn @guangy10