Ask HN: How to avoid AI Dungeon-style bills? I’d like to share something similar
We’ve trained a GPT-2 1.5B model on chess PGN notation. Surprisingly, it’s not bad after only a day of training: https://lichess.org/UMyang4z
(Or rather, it’s not bad up until midgame, at which point it usually blunders. We think it’s because it’s “playing blindfolded” due to the fact that it’s trained solely on PGN notation, as opposed to encoding the full board state each move.)
We’d love to release a Colab demo similar to AI dungeon. But as with AI dungeon, our model is 5.6GB. Downloading from a GCE bucket would cost $0.056 per click, if I understand the outgoing bandwidth pricing model.
Our options seem to be:
1. Download the model via BitTorrent in a colab notebook
2. set up a server to power the demo rather than distribute the model to every client
3. find a host with low bandwidth fees, and write the notebook to download from that
All three have tradeoffs, but #3 seems simplest. Anyone know of a way to distribute 5.6GB to ~500k people for less than a few hundred dollars? BitTorrent might be fine if it can deliver the entire model in less than a couple minutes (otherwise people will get bored and leave).
How many playing sessions a server with a single 2080Ti can support? Is it compute or memory bound? I'd plot num_sessions vs latency (time to compute a move), and estimate the costs for target scale/performance.
Quantization is a good idea, but I've had some bad experiences with bfloat16. (We couldn't get loss to decrease beyond a certain point when using bfloat16.) But that might have been an artifact of training. Still, I'd rather not harm the model if possible. It's hard to get a sense of perceptual quality, and I'm not convinced that validation tests are enough to capture the full nuances of GPT-2.
You're right that a single server would do the trick in this case. It's just so much easier to write a notebook with the logic in it than to set up a server, keep track of sessions, make read-eval-print logic, add error handling, etc. I was hoping to throw a couple hundred dollars at the problem of bandwidth hosting rather than spend time making a server.
A server also implies a fixed $300/mo cost, which is pretty expensive. After the initial demo, we'd probably end up turning the server off. I dislike the idea of the demo breaking after a month or two.
It's hard to quantify how much damage quantization does, but natural language generation is very subtle.