HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
MakazhanAlpamys
Soup
Python2026–2026
MakazhanAlpamys / Soup

Soup

Fine-tune LLMs from one YAML. Layer streaming trains an 8B model on a 4 GB laptop GPU.

2Distinct people
3Mentions
0Explicit recommenders
10.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Fine-tune LLMs from one YAML. Layer streaming trains an 8B model on a 4 GB laptop GPU.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2026-08-04 11:17:57 UTC to 2026-08-04 20:36:12 UTC.

0122026-08-04 11:00:00 UTC to 2026-08-04 12:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsAug 4, 11:002026-08-04 12:00:00 UTC to 2026-08-04 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-04 13:00:00 UTC to 2026-08-04 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-04 14:00:00 UTC to 2026-08-04 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-04 15:00:00 UTC to 2026-08-04 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 4, 15:002026-08-04 16:00:00 UTC to 2026-08-04 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-04 17:00:00 UTC to 2026-08-04 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-04 18:00:00 UTC to 2026-08-04 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-04 19:00:00 UTC to 2026-08-04 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-04 20:00:00 UTC to 2026-08-04 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 4, 20:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 4, 11:002026-08-04 11:00:00 UTC2026-08-04 12:00:00 UTC211
Aug 4, 12:002026-08-04 12:00:00 UTC2026-08-04 13:00:00 UTC000
Aug 4, 13:002026-08-04 13:00:00 UTC2026-08-04 14:00:00 UTC000
Aug 4, 14:002026-08-04 14:00:00 UTC2026-08-04 15:00:00 UTC000
Aug 4, 15:002026-08-04 15:00:00 UTC2026-08-04 16:00:00 UTC000
Aug 4, 16:002026-08-04 16:00:00 UTC2026-08-04 17:00:00 UTC000
Aug 4, 17:002026-08-04 17:00:00 UTC2026-08-04 18:00:00 UTC000
Aug 4, 18:002026-08-04 18:00:00 UTC2026-08-04 19:00:00 UTC000
Aug 4, 19:002026-08-04 19:00:00 UTC2026-08-04 20:00:00 UTC000
Aug 4, 20:002026-08-04 20:00:00 UTC2026-08-04 21:00:00 UTC101

What Hacker News says

3 sources
Author here. The constraint everyone works around is that the frozen base has to fit in VRAM. But during LoRA the base is frozen — read, never written. It doesn't need to live in VRAM, it needs to arrive before the matmul that uses it. So it sits in host RAM and streams into a small pool of pre-allocated VRAM buffers, one decoder layer at a time, prefetched one ahead on a dedicated CUDA stream. Peak VRAM becomes one layer instead of the whole model. Measured on an RTX 3050 Laptop (4 GB, Windows): Llama-3.1-8B in NF4 at 119.6 tok/s, 3.32 GB peak, 100% SM occupancy. Also Qwen2.5-3B with an un-quantized bf16 base at 143 tok/s in 2.15 GB, which is CUDA OOM when trained resident on the same card. Overhead is 1.43x vs resident, measured at 0.5B — the only size on this card with a valid resident baseline, and I publish that baseline so you can c
Read the rest
heck the division. Most of the work wasn't speed, it was correctness. Streaming fails silently: cut the autograd path and the loss still falls because the upper layers keep learning. So the bar was bit-exactness against a resident reference of the same numerics — max abs logit difference 0.0, across nine architecture families in two precisions, as a CI test rather than a one-off. That protocol caught a PEFT dispatch defect producing 0.94 logit divergence with byte-identical weights and adapters, no crash, no warning. Not claiming anything above 8B — 14B NF4 needs ~7.5 GB page-locked against a measured 7.12 GB ceiling here, so I didn't run it. All numbers are Windows, so pessimistic vs Linux. Measurement records, including the ones I threw away: https://github.com/MakazhanAlpamys/Soup/tree/main/benchmarks Write-up: https://doi.org/10.5281/zenodo.21771064 Happy to answer anything about the scheduler or the correctness protocol.
In Show HN: Fine-tune an 8B model on a 4 GB laptop GPU

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.