The output from this model is horrible! It's GPT-2 level babble and repeats entire paragraphs verbatim. It also reuses the same fake citation `(Jenkins, 2010)` over and over again. From the start of their video (which scrolls by fast enough that you don't see the slop clearly...) ``` Ecosystem Services and their impact on the Ecosystem Ecosystem services refer to the services provided by ecosystems to the human socie…
BitNet: Inference framework for 1-bit LLMs
81–90 of 179 posts
Re: BitNet: Inference framework for 1-bit LLMs
#82With how much RAM? How much storage does it requires?
Re: BitNet: Inference framework for 1-bit LLMs
#83The title is misleading — there's no trained 100B model, just an inference framework that claims to handle one. But the engineering is worth paying attention to. I run quantized 70B models locally (M2 Max 96GB, llama.cpp + LiteLLM), and memory bandwidth is always the bottleneck. The 1.58-bit approach is interesting because ternary weights turn matmuls into additions — a fundamentally different compute profile on comm…
> a fundamentally different compute profile on commodity CPU In what way? On modern processors, a Fused Multiply-Add (FMA) instruction generally has the exact same execution throughput as a basic addition instruction
So it's not that individual ops are faster — it's that the packed representation lets each instruction do more useful work, and you're moving far less data from memory to do it.
Re: BitNet: Inference framework for 1-bit LLMs
#84Earlier quoted context omitted.
It comes from (intentionally?) misleading docs: https://github.com/microsoft/BitNet/issues/391 (only suggesting that it's intentional because it's been there so long)
That issue appears to be the one that's wrong. From the technical report > We evaluated bitnet.cpp in terms of both inference speed and energy cost. Comprehensive tests were conducted on models with various parameter sizes, ranging from 125M to 100B. specific configurations for each model are detailed in the Appendix A.
Re: BitNet: Inference framework for 1-bit LLMs
#85It's good to see this getting some continued development. I looked into it last year[1] and I thought it showed a lot of promise so I've been very disappointed that I never saw a newer model. [1] - https://jackson.dev/post/dont-sleep-on-bitnet/
Re: BitNet: Inference framework for 1-bit LLMs
#86but there is no trained 100b param model? "can run a 100B BitNet" is about the inference implementation, not about the existence of any such model
Re: BitNet: Inference framework for 1-bit LLMs
#87I'm curious if 1-bit params can be compared to 4- or 8-bit params. I imagine that 100B is equivalent to something like a 30B model? I guess only evals can say. Still, being able to run a 30B model at good speed on a CPU would be amazing.
At some point you hit information limits. With conventional quantisation you see marked capability fall-off below q5. All else being equal you'd expect an N-parameter 5-bit quant to be roughly comparable to a 3N-parameter ternary, if they are trained to the same level, just in terms of the amount of information they can possibly hold. So yes, 100B ternary would be within the ballpark of a 30B q5 conventional model, w…
Re: BitNet: Inference framework for 1-bit LLMs
#88Re: BitNet: Inference framework for 1-bit LLMs
#89Re: BitNet: Inference framework for 1-bit LLMs
#90The title is misleading — there's no trained 100B model, just an inference framework that claims to handle one. But the engineering is worth paying attention to. I run quantized 70B models locally (M2 Max 96GB, llama.cpp + LiteLLM), and memory bandwidth is always the bottleneck. The 1.58-bit approach is interesting because ternary weights turn matmuls into additions — a fundamentally different compute profile on comm…
I've also always though that it's an interesting opportunity for custom hardware. Two bit addition is incredibly cheap in hardware, especially compared to anything involving floating point. You could make huge vector instructions on the cheap, then connect it to the fastest memory you can buy, and you have a capable inference chip. You'd still need full GPUs for training, but for inference the hardware would be order…
Interestingly, a trit x float multiplier is cheaper than a trit x integer multiplier in hardware if you're willing to ignore things like NaNs.
0 and 1 are trivial, just a mux for identity and zero. But because floats are sign-magnitude, multiply by -1 is just an inverter for the sign bit, where as for integers you need a bitwise inverter and full incrermenter.