
Gene Torres
7 posts





update: qwen 3.6 27b dense q4 just one shotted octopus invaders game on a single 3090. hermes agent drove the whole thing, ~41 tok/s gen 21gb vram at full 262k context, thinking mode on. one prompt in and the canonical multi-file space shooter benchmark out, the same exact prompt i ran on qwen 3.5 27b dense back in march on the same card. 3.5 needed one external scope bug fix before the game would even load on first play. 3.6 needed nothing. 11 of 11 files written, 2411 lines of code, zero steering interventions, zero external fixes, playable on first load. 16 minutes 41 seconds wall clock from prompt to playable. consumer tier king on a single 3090 is locked tonight, and the silicon underneath my desk did not change between march and now. the open source ecosystem just moved the floor. watch it ship itself, the full 16 minutes 41 seconds sped to 3 minutes 45, no human touched the keyboard between the first prompt and the final frame.



before i touch any turbo or quant tricks on the new qwen 3.6-27b dense, i ran a full context sweep on a single 3090. same flags as the march qwen 3.5 baseline. same hardware. the architecture is inherited. exact same vram footprint as 3.5 at every context: 16 gigs at 4k, 18 at 128k, 21 at 262k, 23 at the 376k vram wall. and 13.7 percent faster on identical config. 40.13 tok/s vs 35.30. flat curve from 4k to the wall. next is autonomous agent tasks on hermes agent. single file edits, multi file changes, tool calls, ui builds. i post results as they land, you judge. octopus invaders closes the run as the standard benchmark.


@sudoingX @Teknium @NousResearch hey sudo, is there a way to utilize my 3090 safely with hermes agent and a local model if I have the 3090 in my windows system? I saw that you can use WSL but not sure if thats secure enough
