‹ BackHN Continuity

Thread

Ember-1

589 points · 249 comments · gmays

  1. GodelNumbering · · focus · HN ↗
    This is the golden age of model training. Some days ago, I decided I wanted a local CPU only model that can perform exceptionally well for English to Bash translation (to avoid the googling for command syntax). I got a bunch of subagents to generate large amount of training data (140k+ samples), got the Qwen 3 0.6B base model, pointed Astra at it, and off to the races. It trained for 2 days (on and off) and I got a surprisingly good model for my task! The total active time I spent was a few hours. And it is still improving, what a time to be alive!
    1. shriphani · · focus · HN ↗
      what hardware are you using to train?
      1. GodelNumbering · · focus · HN ↗
        I didn't have a local GPU, so I asked it to go out and find hardware. It found a google TPU v6e which seemed reasonably priced. I gave it my google api key. I told it to use TPU only when training and bring it down afterwards. That's about it.
        1. otterley · · focus · HN ↗
          What kind of observability did you have over this process? I’m interested in how my peers are operating these efforts.
          1. GodelNumbering · · focus · HN ↗
            On the cloud side, nothing valuable existed, so the training couldn't ruin anything it didn't create. On the laptop side, I usually ask the agents to create named scripts for everything it needs to access, then those local script directory is green-lit with approve all. For cost, I kept giving it new budget in the 20-30 dollar increments.

            I had to intervene a few times. For instance, as smart as the models are said to be (Astra), it would copy the full training run, train on the server, pull every checkpoint to the local machine, then run tests, update. So, the bandwidth bill was as high as training bill for the first 6 hours. It could have simply tested each checkpoint on the server, saved time and money, didn't occur to it until I said.

            1. otterley · · focus · HN ↗
              Perhaps I wasn’t clear. What kind of instrumentation and alerting, if any, did you employ to keep an eye on it?
              1. GodelNumbering · · focus · HN ↗
                instrumentation: scripts to watch the runs, measure, report. alerting: none, the model was access limited and constrained by other means.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.