Sure. Why purchase a H200 if you can go with an ESP32 ^^
replyBlowing more than 800kb on essentially an http api wrapper is actually kinda bad. The original Doom binary was 700kb and had vastly more complexity. This is in C after all, so by stripping out nonessential stuff and using the right compiler options, I'd expect something like this to come in under 100kb.
reply> vastly more complexity.
replyDoom is ingenious, but it is not terribly complex IMHO, not compared to a modern networking stack including WiFi driver. The Doom renderer charm is in its overall simplicity. The AI is effective but not sophisticated.
Doom had the benefit of an OS that included a lot of low-level bits like a net stack. This doesn’t! That 800kB includes everything it would need from an OS too.
replyyah my back of the envelope math..
replythe “app logic”/wrapper pieces come out to about 25kb
WiFi is 350 Tls is 120 and certs are 90!
yeah i sandbagged the size just a little to start (small enough to fit on the c3, 888 picked for good luck & prosperity; I even have a build that pads to get 888 exactly), so i can now try reduce some of it as an exercise etc.
replybut 100kb you’re not gonna see :) this has WiFi, tls, etc. doom didn’t need those
haha well I got something ridiculous coming soon for zclaw that will kinda work on board.. will require the S3 variant tho, needs a little more memory. Training it later today.
replydeleted
replyright, 888 kB would be impossible for local inference
replyhowever, it is really not that impressive for just a client
It's not completely impossible, depending on what your expectations are. That language model that was built out of redstone in minecraft had... looks like 5 million parameters. And it could do mostly coherent sentences.
reply > built out of redstone in minecraft
> 5 million parameters