Meta on Tuesday announced the release of Llama 3.1, the latest version of its large language model that the company claims now rivals competitors from OpenAI and Anthropic. The new model comes just three months after Meta launched Llama 3 by integrating it into Meta AI, a chatbot that now lives in Facebook, Messenger, Instagram and WhatsApp and also powers the company’s smart glasses. In the interim, OpenAI and Anthropic already released new versions of their own AI models, a sign that Silicon Valley’s AI arms race isn’t slowing down any time soon.

Meta said that the new model, called Llama 3.1 405B, is the first openly available model that can compete against rivals in general knowledge, math skills and translating across multiple languages. The model was trained on more than 16,000 NVIDIA H100 GPUs, currently the fastest available chips that cost roughly $25,000 each, and can beat rivals on over 150 benchmarks, Meta claimed.

  • Tony N
    link
    fedilink
    English
    112 months ago

    I’ve got llama 3.1 8b running locally in open webui. What do you mean it’s bugged with llama.cpp?

    • @[email protected]
      link
      fedilink
      English
      9
      edit-2
      2 months ago

      llama.cpp, the underlying engine, doesn’t support extended RoPE yet. Basically this means long context doesnt work and short context could be messed up too.

      I am also hearing rumblings of a messed up chat template?

      Basically with any LLM in any UI that uses a GGUF, you have to be very careful of bugs you wouldn’t get in the huggingface-based backends. A lot of models run without errors, but not quite right.

      • FaceDeer
        link
        fedilink
        12 months ago

        I wouldn’t call it a “dud” on that basis. Lots of models come out with lagging support on the various inference engines, it’s a fast-movibg field.

        • @[email protected]
          link
          fedilink
          English
          12 months ago

          Yeah, but it leaves a bad initial impression when all the frontends ship it and the users aren’t aware its bugged.