Gemini 3.6 Flash vs GLM-5.3-Flash
何时用哪一个
当音频是输入的一部分时,请选择 gemini-3.6-flash:它接受文本、图像、视频和音频(音频输入为每百万 token $5,缓存为 $0.5),并具有 1048576-token 窗口,知识截止日期为 2026-03。glm-5.3-flash 仅支持文本、图像和视频,但其输入成本低 10x(每百万 token $0.15 对 $1.5),输出成本低 15x($0.5 对 $7.5),并且允许 163840 个输出 token 相比之下为 65536,因此它适合高容量或长篇生成。两者都运行大约一百万 token 的上下文,保留 vision 和 tools,并且无法关闭 thinking。
Benchmark 成绩
厂商公布: Alibaba (Qwen) Anthropic DeepSeek Google Moonshot OpenAI Tencent Z.ai
定价
| Gemini 3.6 Flash | GLM-5.3-Flash | Δ | |
|---|---|---|---|
| 输入 / 1M tokens | $1.5 | $0.15 | 10× |
| 输出 / 1M tokens | $7.5 | $0.5 | 15× |
| 缓存读取 / 1M tokens | $0.15 | $0.03 | 5× |
费率取自构建时的实时目录;每个模型页面均附有当前的费率卡。
它们的位置 — 以该计费单位计费的所有 67 个 聊天 模型的 每 1M token 的输入价格(对数刻度)
能力
| Gemini 3.6 Flash | GLM-5.3-Flash | |
|---|---|---|
| 工具使用 | 是 | 是 |
| 思考控制 | 始终开启 | 始终开启 |
| 结构化输出 | 是 | 是 |
| 提示词缓存 | 隐式 + 显式 | 隐式(自动) |
| 缓存生存时间 | 未公开 | 未公开 |
| 最小缓存前缀 | 4096 个 token | 未公开 |
规格
| Gemini 3.6 Flash | GLM-5.3-Flash | |
|---|---|---|
| 输入模态 | 文本 图像 音频 视频 | 文本 图像 视频 |
| 输出模态 | 文本 | 文本 |
| 知识截止日期 | 2026-03 | - |
| 上下文窗口 | 1M | 1M |
| 最大输出 | 66K | 164K |
| 思考参数 | thinkingLevel | reasoning_effort |
| 允许的值 |
| reasoning_effort
|
| 默认值 | medium | max |
规格转录自各供应商的文档;若供应商未发布某项数据,则直接省略该行,而非进行推断。 完整来源: Gemini 3.6 Flash · GLM-5.3-Flash
单个 Prompt,两个模型 —— 通过网关实测
Gemini 3.6 Flash 通过 · 3 sentences
Enabling reasoning causes the model to generate thousands of internal "thinking" tokens behind the scenes to process logic before delivering the final response. Because our vendor bills us for every token generated—including these intermediate processing steps—our billable output volume per query surged significantly. Since output tokens carry a much higher unit cost than input tokens, this jump in processing volume directly doubled our overall spend.
输出 893 tok (+816 思考) 延迟 4.7 s
GLM-5.3-Flash 通过 · 3 sentences
Enabling reasoning means the model now generates thousands of invisible "thinking" tokens before each visible answer, and we're billed for those hidden tokens at full output rates—our most expensive tier. Since output tokens cost 3–5x more than input tokens, that hidden thinking volume compounds across every request, which is why the bill doubled rather than edged up. If the spend concerns you, the fix is straightforward: route only complex queries to reasoning models and keep simple tasks on standard ones, which can reclaim a meaningful share of that cost without losing accuracy where it matters.
输出 742 tok (+626 思考) 延迟 23.2 s
指令遵循(恰好三句,可数)、受众适配(面向 CFO 的语气),以及下方 token 计量所暴露的隐藏思考计费缺口。
Gemini 3.6 Flash 通过 · 8/8 cases
Here is the fixed function along with an explanation of the bugs: ```python def longest_run(xs): if not xs: return 0 best = 1 cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` ### Explanation The original function initialized `cur` and `best` to `0` and incremented `cur` on matching adjacent items, which meant it was counting identical adjacent *pairs* rather than the total number of *elements* in a run. This caused single-element inputs to skip the loop and return `0` instead of `1`, and undercounted all run lengths by 1 (for example, a run of two items at the end of the list resulted in `cur = 1`). […]
输出 2034 tok (+1768 思考) 延迟 10.0 s
GLM-5.3-Flash 通过 · 8/8 cases
```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 best = max(best, cur) else: cur = 1 return best ``` **The bug:** `cur` is supposed to hold the length of the current run, but it's seeded with `0` and reset to `0` on a mismatch instead of `1` — and since the loop starts at index 1, the first element of every run never passes through the `==` branch and so never gets counted at all. That means `cur` actually holds *run length minus 1* for every run, so every run is underreported by one: a single-element input never enters the loop and returns 0 instead of 1, and a run of length n returns n − 1 (e.g., `[3, 3, 3]` returns 2). […]
输出 2462 tok (+2138 思考) 延迟 29.1 s
修复是否真的正确(可运行)、解释的信息密度,以及在一个边界明确的任务上的 token 效率。
Gemini 3.6 Flash 通过 · 5/5 fields, guidance "withheld"
```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": null, "guidance": "withheld" } ```
输出 2843 tok (+2783 思考) 延迟 13.1 s
GLM-5.3-Flash 通过 · 5/5 fields, guidance "Withheld pending the Q4 close"
```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": "Withheld pending the Q4 close" } ``` Notes on judgment calls: revenue of 412 is on a constant-currency basis as stated; growth of "eleven and change" is approximated as 11 since no precise figure is given.
输出 717 tok (+616 思考) 延迟 9.1 s
schema 服从度(不臆造字段)、幻觉压力(guidance 明确被暂缓给出),以及结构化输出路径的差异。
Gemini 3.6 Flash 未命中 · 60 words, 0 banned, 0 questions
72: reducing 73: your 74: monthly 75: token 76: spend. S6 (21): 77: You 78: can 79: easily 80: set 81: custom 82: expiration 83: rules, 84: configure 85: TTL 86: settings, 87: and 88: manage 89: cache 90: invalidation 91: across 92: all 93: vendors 94: from 95: one 96: centralized 97: dashboard. S7 (23): 98: Start 99: optimizing […]
输出 4092 tok (+3929 思考) 延迟 16.3 s
GLM-5.3-Flash 通过 · 120 words, 0 banned, 1 question
Introducing Cross-Provider Prompt Cache, the newest feature in our API gateway. Today, teams send identical prompts to multiple LLM providers and pay full price each time. Why duplicate that work and cost? With Cross-Provider Prompt Cache, your gateway stores prompt-response pairs and serves repeated requests from cache, regardless of which provider handles the call. The result: lower latency, reduced spend, and consistent outputs across OpenAI, Anthropic, Google, and self-hosted models. Configure cache policies per route, set TTLs, and invalidate entries instantly through the dashboard or API. Built-in analytics show hit rates and savings in real time. Enable the cache with a single flag, no code changes required. Available today on all paid plans. Contact sales for enterprise volume pricing details.
输出 2095 tok (+1937 思考) 延迟 20.2 s
约束服从度(字数预算、禁用词表、唯一的那句问句)、文风指纹,以及长度控制。
只需一行代码即可在它们之间切换
两个 ID 都包含在下方的每个选项卡中 — 高亮显示的两行是唯一的修改。相同的端点,相同的密钥,相同的请求结构。
from openai import OpenAI
client = OpenAI(
base_url="https://synthorai.io/v1",
api_key="sk-syn-...",
)
resp = client.chat.completions.create(
model="gemini-3.6-flash",
# model="glm-5.3-flash", # 取消注释此行,注释上一行
messages=[{"role": "user", "content": "Summarize this diff"}],
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://synthorai.io/v1",
apiKey: "sk-syn-...",
});
const resp = await client.chat.completions.create({
model: "gemini-3.6-flash",
// model: "glm-5.3-flash", // 取消注释此行,注释上一行
messages: [{ role: "user", content: "Summarize this diff" }],
});
console.log(resp.choices[0].message.content);curl https://synthorai.io/v1/chat/completions \
-H "Authorization: Bearer sk-syn-..." \
-H "Content-Type: application/json" \
-d '{
"model": "gemini-3.6-flash",
# "model": "glm-5.3-flash", # 取消注释此行,注释上一行
"messages": [{"role": "user", "content": "Hello"}]
}'package main
import (
"context"
"fmt"
"github.com/openai/openai-go/v3"
"github.com/openai/openai-go/v3/option"
)
func main() {
client := openai.NewClient(
option.WithBaseURL("https://synthorai.io/v1"),
option.WithAPIKey("sk-syn-..."),
)
resp, _ := client.Chat.Completions.New(context.TODO(), openai.ChatCompletionNewParams{
Model: "gemini-3.6-flash",
// Model: "glm-5.3-flash", // 取消注释此行,注释上一行
Messages: []openai.ChatCompletionMessageParamUnion{
openai.UserMessage("Summarize this diff"),
},
})
fmt.Println(resp.Choices[0].Message.Content)
}import com.openai.client.OpenAIClient;
import com.openai.client.okhttp.OpenAIOkHttpClient;
import com.openai.models.chat.completions.*;
OpenAIClient client = OpenAIOkHttpClient.builder()
.baseUrl("https://synthorai.io/v1")
.apiKey("sk-syn-...")
.build();
ChatCompletion resp = client.chat().completions().create(
ChatCompletionCreateParams.builder()
.model("gemini-3.6-flash")
// .model("glm-5.3-flash") // 取消注释此行,注释上一行
.addUserMessage("Summarize this diff")
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常见问题
Gemini 3.6 Flash 和 GLM-5.3-Flash 哪个更便宜?
在 输入 / 1m tokens 方面,GLM-5.3-Flash 更便宜($0.15 对比 $1.5,相差 10×)。其他行可能得出相反的结论——上方表格提供了完整信息,实际成本取决于你的组合使用情况。
我可以在不进行两次集成的情况下,对 Gemini 3.6 Flash 和 GLM-5.3-Flash 进行 A/B 测试吗?
可以。两者均通过同一个兼容 OpenAI 的端点提供服务,并使用同一把 API 密钥——切换只需更改一行模型字符串,因此你可以将一部分流量路由到各个模型并直接比较账单。
Gemini 3.6 Flash 和 GLM-5.3-Flash 支持提示词缓存吗?
是的 —— 两者对缓存读取的计费均低于其输入费率,因此热前缀工作负载的成本低于标价。准确的缓存读取行位于上方的定价表中。