memdoor/examples/workflows/team-solve at main · guregodevo/memdoor
github.com
Coding workflow harness that makes a small model beat a frontier one - guregodevo/memdoor
    • ☆ Yσɠƚԋσʂ ☆@lemmy.mlOP
      6·
      2 days ago

      You’d need around 64gb vram to run 27b model at q6/8. You don’t have to run multiple models at the same time though, since the same model can work all the different roles sequentially.

      • frigge@lemmy.ml
        3·
        2 days ago

        I’ve been running the Ridge-GGUF version on my RX 9070 XT with ~60-80k contextsize with q4 kv cache quantization. Everything fits completely in 16GB VRAM

          • frigge@lemmy.ml
            3·
            2 days ago

            I have nothing really to compare it to in terms of the big ones because i refuse to give anthropic/openai any money. But i have used this qwen model in opencode to port an old CUDA/Optix based project to HIP and that worked fairly well. Not an overly complex refactor to be honest because 99% is just replacing the cuda prefix everywhere with hip, but it did fix the CMakeLists.txt for me and ported the optix prime acceleration structure to hipRT as well. I also let it vibecode a react based portfolio page because i have absolutely 0 knowledge of web development and refuse to learn it because i think it is insane and that turned out perfectly fine as well.

            So it is absolutely usable for real world projects and the performance is quite OK as well with ~35tok/s. If i up the context size to the full 256k window, the performance drops to 5 tok/s, which is ok, if i let it do a boring refactor over night but at that point it isn’t faster than running DeepSeekV4.1-Flash-1017 through Strata and that one is much closer to the current SotA.

            Definitely exciting times. We are close to being able to run very capable LLMs locally that are more than good enough for development. I am personally not a fan of 100% vibe coded projects anyway, because i like to architect things myself, so letting it go in smaller steps and/or help be with the boring stuff is absolutely fine. Unless the project is some personal stuff that just needs to solve one simple problem then vibe coding is fine imho.

            • ☆ Yσɠƚԋσʂ ☆@lemmy.mlOP
              4·
              2 days ago

              Yeah, that sound pretty usable, and seems like making the harness smarter can up the quality quite a bit. And completely agree about architecting things yourself. I find you want to basically do all the scaffolding, and lay out how the project looks like in terms of structure, the call graph, etc., and then let the model fill in the details. But also like you say, for something that’s a throwaway, or a small personal project to scratch an itch, it doesn’t really matter.

  • marius@feddit.org
    2·
    3 days ago

    Which harness you guys use with this qwen? I use it with open code 2, but it always end up in a loop after just a couple of prompts