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.

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

Weight Cache Follow Up #9301

Open
mcr229 opened this issue Mar 14, 2025 · 0 comments
Open

Weight Cache Follow Up #9301

mcr229 opened this issue Mar 14, 2025 · 0 comments
Assignees
Labels
enhancement Not as big of a feature, but technically not a bug. Should be easy to fix triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Milestone

Comments

@mcr229
Copy link
Contributor

mcr229 commented Mar 14, 2025

For production use cases Tensor FQN might not be safe, we should look at giving better named keys to tensor weights. Perhaps using sha256 or md5 hash of bytes would provide better guarantees around collision, though this locks us into 32/64 byte named keys.

@mcr229 mcr229 added enhancement Not as big of a feature, but technically not a bug. Should be easy to fix triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module labels Mar 14, 2025
@mcr229 mcr229 self-assigned this Mar 14, 2025
@mcr229 mcr229 moved this to Backlog in ExecuTorch - CPU Mar 14, 2025
@mcr229 mcr229 added this to the 0.6.0 milestone Mar 14, 2025
@mcr229 mcr229 moved this from Backlog to Ready in ExecuTorch - CPU Mar 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Not as big of a feature, but technically not a bug. Should be easy to fix triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
Status: Ready
Development

No branches or pull requests

1 participant