pytorch / pytorch/executorch

Freeing unpacked weights immediately after packing

Open
#9,013 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

module: xnnpack triaged
Dominant language
Python
Stars
5k
Forks
1.2k
Avg merge
2d 10h
Merged PRs (30d)
581

Description

cc @digantdesai @mcr229

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

No file, test, or entry point is named in the issue. Locate the weight-packing path first, then identify where packed and unpacked weights are retained; done should be confirmed by relevant tests showing unpacked weights are released immediately after packing.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, machine-learning
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.