aj • snowops.dev (@snowopsdev) header
aj • snowops.dev (@snowopsdev) profile picture

https://teapawt.net/t.co/YZtDAdykYf curiosity put to work. move fast without losing the details.

New Jersey
Joined February 2026
Replying to @thsottiaux
calendar updated
231
Replying to @thsottiaux
updated calendar
79
tested four ways to run AI models on Intel's 32 GB Arc Pro B65. The fastest tool depends on the job: • One person writing code: Intel's vLLM, 1.7× faster than llama.cpp • 8 people at once: exl3xpu, 5.5× more total output • A ~50-page prompt: exl3xpu, 2.5× sooner to start answering • A huge 125B model on one card: Strata, 3.6× faster than llama.cpp • Easiest to set up*: still llama.cpp Every comparison is against llama.cpp at its fastest, with the same tests. Full numbers below. *technically all are easy to setup when you just point your agent to the work 🤷‍♂️
1
3
35
calendar updated
Day 18/ Decisions API is GA, OpenResponses joined the Linux Foundation, we shipped some performance improvements and Uber is going all-in on codex & work. But yes… that’s a reset!
1
23
have been playing around more with turning my old CarThing from Spotify into my dedicated @t3dotcodes notification thingy. added in some useful full screen alerts for when a thread needs my attention. actually liking this more than I thought I would. definitely dont need to buy into those fancy "dedicated ai controllers"...just reuse old hardware and point your agent at it and let it rip.
1
23
T3 code info streaming to my Spotify CarThing.
1
2
102
Anyone remember the Spotify CarThing? Well I decided this morning to recycle it to get a quick view on subs usage and t3 code info. @theo Not exactly the most “useful” but reusing old hardware is fun.
1
24
Update
Day 16/ You can now cache for 12h in the API and for logged in users across Codex & Work we keep cache forever and you don’t have any penalty for coming back to an old conversation or resuming after a few hours and are now guaranteed to hit the cache.
9