‹ BackHN Continuity

Thread

One month coding with GLM 5.3 Flash

228 points · 180 comments · ThibWeb

  1. andai · · focus · HN ↗
    That pareto graph isn't very helpful because it shows cost per token, but some models are way more token hungry than others. There are also massive differences in speed to complete a task.

    My two favorite graphs are AA's A Index vs Time Per Task and AA Index vs Cost Per Task.

    <a href="https:&#x2F;&#x2F;artificialanalysis.ai&#x2F;#intelligence-comparison-tabs" rel="nofollow">https:&#x2F;&#x2F;artificialanalysis.ai&#x2F;#intelligence-comparison-tabs

    <a href="https:&#x2F;&#x2F;artificialanalysis.ai&#x2F;?intelligence-comparison=intelligence-vs-time-per-task#intelligence-comparison-tabs" rel="nofollow">https:&#x2F;&#x2F;artificialanalysis.ai&#x2F;?intelligence-comparison=intel...

    1. ThibWeb · · focus · HN ↗
      ah my bad, I’ve switched the visual to A index by cost per task. Note the blog post’s plot is filtered further than AA’s, based on what models are available with inference providers we can actually work with (Europe only). Vibe-coded filtering is here (very rough): <a href="https:&#x2F;&#x2F;pareto-eco-sum.netlify.app&#x2F;" rel="nofollow">https:&#x2F;&#x2F;pareto-eco-sum.netlify.app&#x2F;
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.