Model reference · open weights

openchat-3.5-1210

LLMs openchat Text gen 1 build Open weights 1k dl/mo

openchat-3.5-1210 is an open-weight language model from openchat. openchat-3.5-1210 (BF16) weighs 14.5 GB; the smallest configuration that runs it is 2× RTX 3060 12 GB.

What it is

Released byopenchat
TypeLanguage models
TaskText gen
Parameters (lead)7.2B
Context8,192 tokens
Runs withtransformers
Based onmistralai/Mistral-7B-v0.1
Released2023-12-12
Popularity1k downloads / month
Weights14.5 GB (openchat-3.5-1210 (BF16), file size)
LicenceOpen weights

What it runs on

Memory and cards for openchat-3.5-1210 (BF16)

Weights 14.5 GB (file size) · KV cache 0 MB per 1,000 tokens of context, at 16 bits (vLLM's default for this build; an 8-bit cache halves it) · plus 1.1 GB a request for its sliding-window layers · runtime overhead from 647 MB on a small card · context up to 8,192 tokens.

CardRequests at once
8K tokens each
Requests at once
32K tokens each
Longest single
request
Counted
memory
RTX 3060 12 GB———11.6 GB
RTX 4060 Ti 16 GB———15.4 GB
RTX 3090 24 GB7—all 8K23.4 GB
RTX 4090 24 GB7—all 8K23.4 GB
RTX 5090 32 GB14—all 8K31.0 GB
L40S 48 GB26—all 8K44.0 GB
A100 80 GB58—all 8K78.2 GB
H100 80 GB55—all 8K78.1 GB
RTX PRO 6000 Blackwell 96 GB70—all 8K93.8 GB
DGX Spark (GB10) 128 GB unified83—all 8K107 GB
H200 141 GB111—all 8K138 GB
B200 180 GB146—all 8K176 GB
2× RTX 3060 12 GB
tensor parallel
6—all 8K11.6 GB a card
2× RTX 4060 Ti 16 GB
tensor parallel
14—all 8K15.4 GB a card
2× RTX 4090 24 GB
tensor parallel
28—all 8K23.4 GB a card
2× RTX 3090 24 GB
tensor parallel
28—all 8K23.4 GB a card
Memory needed at each load
Requests at once8K tokens each32K tokens each
116.2 GB—
520.5 GB—
823.7 GB—
1632.3 GB—
3249.5 GB—
6483.8 GB—

On one card, with vLLM's small-card settings (2,048 tokens a step). Cards of 70 GB and more reserve more per request and more overhead — each row above uses its own card's settings.

Estimates, not measurements, checked against published vLLM startup logs. The weights are the build's file size; the cache is calculated from its config (attention with sliding-window layers); the overhead is an estimate of vLLM's own memory with that card's default settings. "Requests at once" is how many requests of that length vLLM admits — its reservation at full length, with --max-model-len set to that length; requests that stay shorter fit more. "Longest single request" is the most one request can hold there: below the model's maximum, vLLM starts only with --max-model-len set at or under it. "Counted memory" is vLLM's default 92 % of what CUDA reports for the card (the DGX Spark: about 100 GiB of its shared 128 GB). A tensor-parallel split pools the cards' memory and speeds each token up, at the cost of the link between them; a layer split (llama.cpp) holds more but does not make one request faster. Assumes vLLM 0.10 or later.

From the model card

What openchat says about openchat-3.5-1210

font-family: 'Helvetica'; color: black; font-weight: bold;">OpenChat-3.5🚀

Read the full model card
  1. Usage
  2. Benchmarks
  3. Limitations
  4. License
  5. Dataset Details
  6. Citation
  7. Acknowledgements

To use this model, we highly recommend installing the OpenChat package by following the installation guide in our repository and using the OpenChat OpenAI-compatible API server by running the serving command from the table below. The server is optimized for high-throughput deployment using vLLM and can run on a consumer GPU with 24GB RAM. To enable tensor parallelism, append --tensor-parallel-size N to the serving command.

Once started, the server listens at localhost:18888 for requests and is compatible with the OpenAI ChatCompletion API specifications. Please refer to the example request below for reference. Additionally, you can use the OpenChat Web UI for a user-friendly experience.

If you want to deploy the server as an online service, you can use --api-keys sk-KEY1 sk-KEY2 ... to specify allowed API keys and --disable-log-requests --disable-log-stats --log-file openchat.log for logging only to a file. For security purposes, we recommend using an HTTPS gateway in front of the server.

ModelSizeContextWeightsServing
OpenChat 3.5 12107B8192Huggingfacepython -m ochat.serving.openai_api_server --model openchat/openchat-3.5-1210 --engine-use-ray --worker-use-ray

💡 Default Mode (GPT4 Correct): Best for coding, chat and general tasks

curl http://localhost:18888/v1/chat/completions \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openchat_3.5",
    "messages": [{"role": "user", "content": "You are a large language model named OpenChat. Write a poem to describe yourself"}]
  }'

🧮 Mathematical Reasoning Mode: Tailored for solving math problems

curl http://localhost:18888/v1/chat/completions \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openchat_3.5",
    "condition": "Math Correct",
    "messages": [{"role": "user", "content": "10.3 − 7988.8133 = "}]
  }'

Conversation templates

💡 Default Mode (GPT4 Correct): Best for coding, chat and general tasks

GPT4 Correct User: HelloGPT4 Correct Assistant: HiGPT4 Correct User: How are you today?GPT4 Correct Assistant:

🧮 Mathematical Reasoning Mode: Tailored for solving math problems

Math Correct User: 10.3 − 7988.8133=Math Correct Assistant:

⚠️ Notice: Remember to set `` as end of generation token.

The default (GPT4 Correct) template is also available as the integrated tokenizer.chat_template, which can be used instead of manually specifying the template:

messages = [
    {"role": "user", "content": "Hello"},
    {"role": "assistant", "content": "Hi"},
    {"role": "user", "content": "How are you today?"}
]
tokens = tokenizer.apply_chat_template(messages, add_generation_prompt=True)
assert tokens == [1, 420, 6316, 28781, 3198, 3123, 1247, 28747, 22557, 32000, 420, 6316, 28781, 3198, 3123, 21631, 28747, 15359, 32000, 420, 6316, 28781, 3198, 3123, 1247, 28747, 1602, 460, 368, 3154, 28804, 32000, 420, 6316, 28781, 3198, 3123, 21631, 28747]

We've included evaluator capabilities in this release to advance open-source models as evaluators. You can use Default Mode (GPT4 Correct) with the following prompt (same as Prometheus) to evaluate a response.

###Task Description:
An instruction (might include an Input inside it), a response to evaluate, a reference answer that gets a score of 5, and a score rubric representing a evaluation criteria are given.
1. Write a detailed feedback that assess the quality of the response strictly based on the given score rubric, not evaluating in general.
2. After writing a feedback, write a score that is an integer between 1 and 5. You should refer to the score rubric.
3. The output format should look as follows: "Feedback: (write a feedback for criteria) [RESULT] (an integer number between 1 and 5)"
4. Please do not generate any other opening, closing, and explanations.

###The instruction to evaluate:
{orig_instruction}

###Response to evaluate:
{orig_response}

###Reference Answer (Score 5):
{orig_reference_answer}

###Score Rubrics:
[{orig_criteria}]
Score 1: {orig_score1_description}
Score 2: {orig_score2_description}
Score 3: {orig_score3_description}
Score 4: {orig_score4_description}
Score 5: {orig_score5_description}

###Feedback:
Model# ParamsAverageMT-BenchHumanEvalBBH MCAGIEvalTruthfulQAMMLUGSM8KBBH CoT
OpenChat-3.5-12107B63.87.7668.949.548.061.865.377.361.8
OpenChat-3.57B61.67.8155.547.647.459.164.377.363.5
ChatGPT (March)*?61.5

Quoted from the model card on Hugging Face — the full card is behind the Hugging Face link above.

© 2026 AxForge · EU-hosted AI infrastructure Pricing Docs Trust Privacy Terms