임베드 보드

사용자 등록 기반 큐레이션

Тож я протестував GPT-6.1 Sol на реальній роботі: 2 репозиторії, 105 навмисно доданих багів. Знайди й виправ усе, що зможеш. На відміну від GPT-6 Sol, який був просто понерфленою GPT-5.6 Terra, ця — справжня. Результати: - GPT-6 Astra (max): 45 за $33 - GPT-6.1 Sol (max): 44 за $6.56 - GPT-5.6 Sol (max): 43.5 за $95.35 - Opus 5.5 (max): 41.7 за $58.53 - GPT-6 Sol (max): 29.3 за $9.33 З такою моделлю 50% знижка на тариф за $200 вже не має значення. n=1. Більше запусків та результатів на інших рівнях зусиль з'явиться у цьому треді ove

Тож я протестував GPT-6.1 Sol на реальній роботі: 2 репозиторії, 105 навмисно д…
0 0 0 0

Коментарі 42

  • @cyberpeterg Відповідь ♥ 0

    @PawelHuryn GPT 6.1 sol has been absolutely stupid for me. https://x.com/cyberpeterg/status/2105313537543303596?s=20

    Оригінал
    • @PawelHuryn Вкладена ♥ 8

      @TheHasnainK The answer key and specific bugs aren't public, but you can see a bug coverage here: https://bughunt.productcompass.pm/

      Оригінал
        • @PawelHuryn Вкладена ♥ 1

          @tf3y @TheHasnainK You can include it on the website. It's barely better than Opus 5.5. No point in using it right now, IMO.

          Оригінал
          • @PawelHuryn Вкладена ♥ 1

            @tf3y @TheHasnainK @tf3y, it's a single run, so the coverage looks less advanced. This single score is 1.3 points higher than the average for Opus 5.5 (n=3)

            Оригінал
  • @borgerntendies Відповідь ♥ 0

    @PawelHuryn @grok sol 6.1 is clearly cutting into OAI's margins. Is this "race to the bottom" reminiscent of early 2000's internet prices? When did this race start? When did it end? Outcomes?

    Оригінал
  • @magdake2876 Відповідь ♥ 0

    @PawelHuryn Просто на подписке за 200$ можно было бы бесконечно пользоваться 6.1 sol ultra и не покупать кредиты, openai это непонравилось😂

    Оригінал
  • @heysrihari Відповідь ♥ 0

    @PawelHuryn do the fixes get checked for new bugs too, or just whether the planted ones are gone?

    Оригінал
  • @thierrybijou Відповідь ♥ 0

    @PawelHuryn Opus 5.5 at 41.7 for $58.53 against 6.1 Sol at 44 for $6.56 is the line that matters here. Once you log a few more runs, I'd love to see whether the misses overlap or whether Opus catches bugs Sol never touches, because that decides routing versus just picking one.

    Оригінал
  • @turkelitopcusu Відповідь ♥ 0

    @PawelHuryn how much you got from openai? "With a model like this, the 50% cut to the $200 plan doesn't matter." all these are just for this sentences to plant the idea it's ok. it's not ok bro.

    Оригінал
  • @Sercanvwty Відповідь ♥ 0

    @PawelHuryn Short: 6.1 Sol finally sits on the right shelf. Not the bug king. The king of cost per bug found.

    Оригінал
  • @icauro_ Відповідь ♥ 0

    @PawelHuryn There is alternative 3D visualization of the results, can make 3 axis comparison easier. https://icauro.com/toabundance?benchmark=bug-hunt

    Оригінал
  • @AlessandroScola Відповідь ♥ 0

    @PawelHuryn The only problem? "remove the xx button from the page" ... 'valutating bla bla bla' ..... 10 minutes later 'button removed, i'll now verify if the button is not visible' ..... . 15 minutes... 'the button is removed and not present on the page' (but still in temp page) 30m tot

    Оригінал
  • @travisfont Відповідь ♥ 0

    @PawelHuryn A bit useless to show the highest level of AI. The real challenge comes when you test on medium.

    Оригінал
  • @IngIndexado Відповідь ♥ 0

    @PawelHuryn In terms of criticality (identifying more impactful bugs), was GPT-6.1 Sol on par with GPT-6 Astra and Fable 5.1? Btw, thanks for this, this is gold! 🤝

    Оригінал
  • @OM56271680 Відповідь ♥ 0

    @PawelHuryn GPT 6.1 Sol is basically a telenovela: the cast is great, young, and gorgeous, the costumes are stunning, but almost nothing actually happens. You could easily skip four episodes and still not miss a beat.

    Оригінал
  • @jakestone2306 Відповідь ♥ 1

    @PawelHuryn Glad you're adding n=3. I'd put a bug-by-bug stability view next to the totals: fixing 44 different bugs each run creates a different review workload from reliably fixing the same 44.

    Оригінал
    • @PawelHuryn Вкладена ♥ 2

      @jakestone2306 It's not 100% deterministic. Bugs differ a lot between runs. This view: https://bughunt.productcompass.pm/?preset=featured&view=coverage

      Оригінал
      • @SvenMeyer Вкладена ♥ 0

        @PawelHuryn @jakestone2306 GPT-5.6 Sol + GPT-6.1 Sol looks like an interesting combination or is it just a coincidence that one finds bugs at the end the other one missed ?

        Оригінал
        • @SvenMeyer Вкладена ♥ 0

          @PawelHuryn @jakestone2306 Uh, just saw that GPT-5.6 Sol is horrible expensive, I would get away cheaper with Astra ! ... but combination of multiple models might be a cost effective approach to try.

          Оригінал
          • @jakestone2306 Вкладена ♥ 0

            @SvenMeyer It could be complementary coverage, or just run-to-run variation. I'd compare two passes of one model with one pass each of two models, at the same total budget. Count newly fixed bugs on the second pass, not just the combined score.

            Оригінал
  • @lau65536 Відповідь ♥ 0

    @PawelHuryn For finding bugs, does it make sense to first run Sol 6.1. Then run Opus 5.5 with the knowledge of known bugs from Sol. Can it lower the total cost while catching more bugs?

    Оригінал
  • @WirMachenAuf_de Відповідь ♥ 1

    @PawelHuryn i used 6.1 for bug findings. it was much better than opus 5.5. but opus is much better in performance, design and smart code

    Оригінал
  • @laugh2MuchSoMB Відповідь ♥ 0

    @PawelHuryn 跟我在實際工作中使用6.1 sol xhigh 的體感一樣,有好又省!好像有點慢?

    Оригінал
  • @sapientwilight Відповідь ♥ 0

    @PawelHuryn I would advise against testing every model on Max reasoning. Most tend perform better on Medium or High, like my test here where Terra and Luna both suffer on Max:

    Оригінал
  • @taoyetouzi Відповідь ♥ 0

    @PawelHuryn The real story is the price ratio, not the score — 44 bugs for $6.56 vs 45 for $33. At one-fifth the cost you can just run five passes and brute-force the gap. Makes the whole "Astra got shelved for safety" line look more like a pricing problem.

    Оригінал
  • @JDisclosur94877 Відповідь ♥ 0

    @PawelHuryn Would be nice to see amount of slop and regressions introduced. Gemini for me was terrible for fixing things, it wasn't using good architecture, patterns and introduced a lot of regression. But the results may actually vary by how good your agentic context is in the workspace.

    Оригінал
스크롤하면 더 불러옵니다