ml-explore / ml-explore/mlx-examples
Possible to reduce disc writes when converting models?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Hello!
I am regularly converting models to MLX and uploading them to HF. When I find a model I upload both q3, q4, q6, q8 and full mlx version.
This is causing a lot of disc writes and I'm kind of worried that I'm speedrunning my new macbook that has 500gb ssd to failure (I've written and deleted several tb of models in last 2 weeks).
Would it be possible to somehow not save the output of the conversion to disc and just kind of convert it and upload straight to HF? Or somehow run this on an external drive or something? Or something else that would minimize how much data is written to the disc when converting multiple quants of the same model?
I'm not sure exactly of the details of how it is converting and saving it to disc but would much appreciate some help with this as its a fun hobby for me to convert models.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names model conversion to MLX and upload to Hugging Face, but no file, test, or entry point. Begin by tracing the conversion and upload flow in the repository; done would require an agreed approach that reduces local disk writes while preserving the requested quantized outputs and upload behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- huggingface, python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100