git404hub

what is minimax-m3-tp3-rtx6000 fr?

bitman-sachs/minimax-m3-tp3-rtx6000 — explained in plain English

Analysis updated 2026-05-18

2ShellAudience · ops devopsComplexity · 5/5Setup · hard

tl;dr

Instructions and a code patch for running the huge MiniMax-M3 AI model, including image understanding, split across three GPUs at once.

vibe map

mindmap
  root((minimax m3 tp3))
    What it does
      Runs MiniMax M3 model
      Splits across 3 GPUs
      Supports images
    Tech stack
      vLLM
      Docker
      CUDA
    Use cases
      Serve chat API
      Long context tasks
      Multimodal input
    Key fix
      Patch divide function
      Replicate vision tower
      Avoid vLLM crash

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Run the MiniMax-M3 model across three GPUs when it does not fit on one or two.

VIBE 2

Serve a chat API that can understand both text and images from this model.

VIBE 3

Fix vLLM crashes caused by model components that cannot be split evenly across GPUs.

VIBE 4

Support very long conversations by using a 240,000 token context window.

what's the stack?

ShellPythonDockervLLMCUDA

how it stacks up fr

bitman-sachs/minimax-m3-tp3-rtx6000brandur/heroku-buildpack-mono-buildchrisor-dev/claude-autosync
Stars222
LanguageShellShellShell
Last pushed2012-01-27
MaintenanceDormant
Setup difficultyhardmoderatemoderate
Complexity5/52/53/5
Audienceops devopsops devopsdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · hard time til it works · 1day+

Needs 3 high-end GPUs (RTX PRO 6000, 96GB each), Docker, and a large model download of roughly 243GB.

in plain english

This project is a guide and set of scripts for running a very large AI language model called MiniMax-M3 on three powerful graphics cards (GPUs) at the same time, so the model's work is split across all three. MiniMax-M3 is a huge model, made up of many smaller expert networks that only partially activate for each request, and it also understands images, not just text. The main challenge the author solved is a math problem. When you split a model's work across 3 GPUs, every part of the model has to divide evenly by 3. The main language part of the model does, once a patch is applied, but the part that understands images has 16 internal attention heads, and 16 does not divide evenly by 3. Normally this crashes the software used to run the model, called vLLM, before it can even load. The fix is a small change to a few lines of vLLM's code. Instead of crashing when something cannot be split evenly across GPUs, the code now copies that piece, in this case the image understanding part, onto all three GPUs instead of splitting it. The main language model is still divided across the GPUs as normal. This means the setup can now handle both text and images, unlike an older workaround that only supported text. The README includes benchmark tables showing how many words per second the model produces at different amounts of remembered context, up to 240,000, and shows perfect scores on a memory test that checks whether the model can find specific information hidden in a long block of text. It also confirms that sending images to the model, through a standard chat API, works correctly. Beyond the explanation, the README gives full step by step instructions: the exact Docker command to start the container, the exact code to apply the patch, and the command to launch the model server, along with tables describing hardware requirements and memory usage per GPU.

prompts (copy fr)

prompt 1
Walk me through the Docker command in this repo step by step and explain what each flag does.
prompt 2
Explain why 16 attention heads cannot be split across 3 GPUs and how this patch fixes it.
prompt 3
Help me adapt this vLLM launch command for a different number of GPUs.
prompt 4
Summarize the VRAM budget table so I know if my hardware can run this setup.

Frequently asked questions

what is minimax-m3-tp3-rtx6000 fr?

Instructions and a code patch for running the huge MiniMax-M3 AI model, including image understanding, split across three GPUs at once.

What language is minimax-m3-tp3-rtx6000 written in?

Mainly Shell. The stack also includes Shell, Python, Docker.

How hard is minimax-m3-tp3-rtx6000 to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is minimax-m3-tp3-rtx6000 for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.