Answer short product questions.
Retrieve the relevant help paragraph and ask for a concise response. Use a bounded answer length and a clear fallback when the excerpt does not cover the question.
Qwen3-8B is a text model with switchable thinking and non-thinking modes. Run it on AI Fabric for product chat and support triage, choosing when a request needs a short answer or deeper reasoning.
€5 in free credits for every new customer.
Plan your deploymentAI Fabric access is opening gradually. GPU configuration is confirmed during onboarding.
Keep routine answers short and reserve deeper reasoning for requests that need it. Start with a task your team can score against a known answer or resolution.
Retrieve the relevant help paragraph and ask for a concise response. Use a bounded answer length and a clear fallback when the excerpt does not cover the question.
Sort incoming messages into a small set of categories and urgency flags. Evaluate ambiguous messages separately from obvious ones before choosing which decisions can be automated.
Use application rules to select the thinking mode for multi-step problems. Compare the extra delay against resolved requests instead of enabling deeper reasoning for every greeting.
Model capabilities and upstream setup: Qwen3-8B publisher reference. Reviewed .
Deployment preparation
Use the model’s own chat template and configure the thinking mode explicitly. The example disables thinking for a short answer and loads weights in 4-bit precision to leave more room for the runtime.
import torch
from transformers import (
AutoModelForCausalLM, AutoTokenizer, BitsAndBytesConfig,
)
model_id = "Qwen/Qwen3-8B"
quant = BitsAndBytesConfig(
load_in_4bit=True,
bnb_4bit_compute_dtype=torch.bfloat16,
)
model = AutoModelForCausalLM.from_pretrained(
model_id, quantization_config=quant, device_map="auto",
)
tokenizer = AutoTokenizer.from_pretrained(model_id)
messages = [{"role": "user", "content":
"Explain how a queue separates web requests from workers."}]
text = tokenizer.apply_chat_template(
messages, tokenize=False, add_generation_prompt=True,
enable_thinking=False,
)
inputs = tokenizer(text, return_tensors="pt").to(model.device)
output = model.generate(
**inputs, max_new_tokens=512, do_sample=True,
temperature=0.7, top_p=0.8,
)
print(tokenizer.decode(
output[0][inputs.input_ids.shape[-1]:],
skip_special_tokens=True,
))Python preparation example using 4-bit loading. Validate the exact dependency versions and GPU configuration; this has not been benchmarked on Blade. Transformers quantization setup ↗
GPU memory & performanceUnquantized BF16 weights alone are roughly 16 GB, leaving too little headroom on the 16 GB card. Quantized loading is a starting point for both cards, not a guarantee for arbitrary context or traffic.
In your applicationKeep only the relevant conversation history. Make mode selection observable so unexpected latency can be traced to the actual request settings.
AI Fabric availability & costRTX A4500 (20 GB) and RTX 2000 Ada (16 GB) are the GPU options. Access, runtime settings and billing are confirmed during onboarding. No Blade latency or throughput benchmark is published for this configuration.
A support application can run classification first, fetch the relevant article and then ask for an answer. Treat category validation and retrieval as application code. Escalate unresolved questions with the original evidence instead of asking the model to invent a resolution.
Yes. The upstream chat template exposes enable_thinking. The Python example sets it to false; use the matching controls if you serve the model through another engine.
No. Unrelated history can obscure the relevant evidence and increases memory use. Evaluate a retrieval-first workflow with bounded history.
Track first-token time, complete-response time, correctness and how often a human takes over. Include peak memory at the busiest conversation length you plan to support.
Compare cost per resolved support request across thinking modes. Include conversation length, generated tokens and repeated attempts, not just the number of incoming messages.
The GPU billing unit and idle policy are confirmed during onboarding. Managed Models API rates do not apply to this deployment.
Checkpoint: Qwen/Qwen3-8B. Access requirements and licence: Qwen3-8B publisher reference.