NVIDIA / NVIDIA/Model-Optimizer

LUT-B Support

Open
#2,204 1 comment 0 reactions 1 assignee View on GitHub

@Edwardf0t1 is already working on this.

Since Aug 17, 2026.

question
Dominant language
Python
Stars
3.8k
Forks
604
Avg merge
2d 8h
Merged PRs (30d)
142

Description

How would you like to use ModelOpt

Hi, I am a maintainer of vllm-project/compressed-tensors, and we are looking to do some up-front work to benchmark the LUT-B pathways that Vera Rubin will support, as well as solidify the compression format inside compressed-tensors and the load-up pathway in vllm. We are constrained by the limited technical specs we have seen, and wanted to start a discussion here (as suggested by @Edwardf0t1 in today's vllm sig-quant meeting).

I would be very happy to set up a call to discuss further, if the maintainers of modelopt are interested, to try to align our formats as much as possible. But at the moment, this amounts to 3 questions in particular (in order of importance):

  1. Ref 1 states "LUT-based representations can retain up to MXFP8 accuracy, adding another precision option to the Rubin inference toolbox". Does this mean each codebook tile will require an associated FP8 e8m0 scale? (See Ref 4 for our current checkpoint, which has weight_packed and weight_codebook, but no weight_scale as of yet)
  2. Ref 1 states that Vera Rubin will support a 3-bit lookup table. Just wanted to confirm this isn't configurable beyond 3 bits.
  3. Similar to above, are tile sizes configurable or constrained?

Refs:

  1. Nvidia dev blog -- https://developer.nvidia.com/blog/inside-nvidia-rubin-gpu-architecture-powering-the-era-of-agentic-ai/
  2. WIP compressed-tensors format -- https://github.com/vllm-project/compressed-tensors/pull/801
  3. WIP vllm online quant -- https://github.com/vllm-project/vllm/pull/51880
  4. WIP checkpoint -- https://huggingface.co/bdellabe/Meta-Llama-3-8B-Instruct-LUTB
Who can help?

Anyone involved in adding LUT-B compression support to ModelOpt

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.