‹ BackHN Continuity

Thread

Pareto Front

198 points · 85 comments · binyu

  1. bhanu786 · · focus · HN ↗
    may, anyone explain what is this
    1. chriswarbo · · focus · HN ↗
      If we have a set of things (e.g. language models) and some measures we care about (e.g. cost, speed, whether weights are open, scores for a few benchmarks, etc.), then some of those things will be "pareto optimal" (see below) and some won't. The "pareto front" is the subset that is pareto optimal.

      Some thing is "pareto optimal" when there isn't another thing that's AT LEAST AS GOOD in ALL measures, and BETTER in at least one way. For example, if we say there are no ties (for simplicity), then the cheapest language model is pareto optimal; the fastest model is pareto optimal; those which score highest on each benchmark are pareto optimal; and so on.

      Tradeoffs can also be pareto optimal: for example, if the cheapest model is also slow, then there will be more pareto optimal models which are "cheapest for their speed"; and so on for other tradeoffs (e.g. fastest that achieves a certain benchmark score; cheapest model with open weights; etc.).

      If you're making a decision about which thing to choose, you only need to care about those in the pareto front (since, by definition, anything that's not pareto optimal is objectively worse on at least one measure).

      Pareto optimality does not compare one measure against another: something that's 10000x slower can still be pareto optimal, if it's 1% cheaper than the alternatives. To pick a "best" thing, you could give a weight/importance to each measure, and combine them into an overall score: but that's subjective, and might vary between people and tasks. In contrast, focusing on the pareto front is a way to ignore those things that will never be the best, regardless of weighting.

      1. matsemann · · focus · HN ↗
        I honestly think the wikipedia article is too complicated. My own image example here as an another attempt to explain: <a href="https:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;5ZQIJDb" rel="nofollow">https:&#x2F;&#x2F;imgur.com&#x2F;a&#x2F;5ZQIJDb

        Mapping the cost of something (like an algorithm), and the time it takes (so lower is better for both). 1, 3 and 5 are all optimal in their own sense. No one is strictly better than the other, just different tradeoffs you have to choose yourself. However, you would never choose 2, because for a lower cost you could get the same result choosing 3. Same with 4, 6 and 7, they all have something that&#x27;s both faster and at the same time just as cheap you could choose.

        A pareto front is a bit like the classical &quot;fast, cheap, good, choose 2&quot;. There are always tradeoffs, but if something is both slow, expensive and not better than something that&#x27;s faster and cheaper, it&#x27;s a bad choice, and thus not on the &quot;pareto front&quot;.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.