HNNewShowAskJobs
Built with Tanstack Start
"time to GPT-2", down to 2.91 hours(twitter.com)
58 points by tosh 4 hours ago | 9 comments
  • Cyphase2 hours ago

    https://nitter.net/karpathy/status/2018804068874064198

  • blitzar4 minutes ago

    > GPT-2 (7 years ago): too dangerous to release.

    With the benefit of hindsight you can see the the charitable foundation to benefit mankind was a grift all along.

  • blitzar5 minutes ago

    > GPT-2 (7 years ago): too dangerous to release.

    With the benefit of hindsight you can see the heads of the charitable foundation to benefit mankind were grifters all along.

  • janalsncm3 hours ago

    Never used gpu spot instances before but I would have to imagine getting interrupted is pretty annoying.

    • somehowadev2 hours ago |parent

      As long as your workload can handle resuming again and your instances aren't heavily in-demand (looking at the eviction rates), the cost saving for us is substantial enough to take the occasional interruption.

      I do wish Azure gave more than the 30 second eviction warning (like AWS) but still useable.

    • hhh3 hours ago |parent

      it depends, our workloads can finish up in under two minutes and shut down without much effort, so we haven’t really noticed it outside of one time when we had no spot capacity.

      • janalsncm3 hours ago |parent

        I guess if checkpointing is set up correctly and your runtime is saved to a docker image it’s feasible. Probably not going to get a 3 hour continuous chunk of time I would assume.

        • direwolf202 hours ago |parent

          When I once used Spot it wasn't that bad. You're likely to have an instance for 3 hours.

      • joeig3 hours ago |parent

        In addition to the two-minute interruption notice, rebalance recommendations[0] allow you to handle interruptions even more gracefully.

        [0] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/rebalanc...