测试结果
Run ID: 20260827-123651-fa1fae11
总请求45
成功 / 失败36/9
成功率80.0%
平均延迟3592 ms
P95 / Tokens8270 / 4710
| 渠道 | 模型 | 成功 | 失败 | 成功率 | 失败率 | 稳定性 | 平均延迟 ms | P95 ms | Tokens | 首个错误 |
|---|---|---|---|---|---|---|---|---|---|---|
| DeepSeek-v4-pro-01 | deepseek-v4-pro | 3/3 | 0/3 | 100.0% | 0.0% | 稳定 | 908 | 1124 | 339 | |
| DeepSeek-v4-pro-04 | deepseek-v4-pro | 3/3 | 0/3 | 100.0% | 0.0% | 稳定 | 986 | 1135 | 339 | |
| DeepSeek-v4-pro-02 | deepseek-v4-pro | 3/3 | 0/3 | 100.0% | 0.0% | 稳定 | 1189 | 1339 | 339 | |
| DeepSeek-v4-pro-03 | deepseek-v4-pro | 3/3 | 0/3 | 100.0% | 0.0% | 稳定 | 1266 | 1516 | 339 | |
| Qwen3.8-Max | qwen3.8-max | 3/3 | 0/3 | 100.0% | 0.0% | 稳定 | 1943 | 2229 | 397 | |
| Kimi K3 - Aliyun Bailian | kimi/kimi-k3 | 3/3 | 0/3 | 100.0% | 0.0% | 稳定 | 2467 | 2955 | 345 | |
| jd-gemini-3.1-pro-preview | gemini-3.1-pro-preview | 3/3 | 0/3 | 100.0% | 0.0% | 稳定 | 2919 | 3388 | 79 | |
| 腾讯 Gemini 3.5 Flash | gemini-3.5-flash | 3/3 | 0/3 | 100.0% | 0.0% | 可用 | 4555 | 5136 | 78 | |
| yulin-gemini-3.7-flash-high | gemini-3.7-flash-high | 3/3 | 0/3 | 100.0% | 0.0% | 可用 | 5289 | 5907 | 502 | |
| qwen3.6-plus | qwen3.6-plus | 3/3 | 0/3 | 100.0% | 0.0% | 可用 | 5695 | 5982 | 959 | |
| Kimi K3 | kimi-k3 | 3/3 | 0/3 | 100.0% | 0.0% | 可用 | 7574 | 8278 | 646 | |
| Kimi K3 - TopenRouter | kimi-k3 | 3/3 | 0/3 | 100.0% | 0.0% | 可用 | 8316 | 18316 | 348 | |
| MiniMax H3 Context IR | MiniMax-H3 | 0/3 | 3/3 | 0.0% | 100.0% | 不稳定 | - | - | 0 | HTTP 400: binding: expr_path=content, cause=missing required parameter |
| pixflow-gemini-3.1-pro-preview | gemini-3.1-pro-preview | 0/3 | 3/3 | 0.0% | 100.0% | 不稳定 | - | - | 0 | HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"} |
| yuling-gpt-5.5 | gpt-5.5 | 0/3 | 3/3 | 0.0% | 100.0% | 不稳定 | - | - | 0 | HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"} |
结果明细
#1 DeepSeek-v4-pro-01
成功
HTTP 200
无输出内容。
#2 DeepSeek-v4-pro-01
成功
HTTP 200
无输出内容。
#3 DeepSeek-v4-pro-01
成功
HTTP 200
无输出内容。
#4 DeepSeek-v4-pro-03
成功
HTTP 200
无输出内容。
#5 DeepSeek-v4-pro-03
成功
HTTP 200
无输出内容。
#6 DeepSeek-v4-pro-03
成功
HTTP 200
无输出内容。
#7 DeepSeek-v4-pro-04
成功
HTTP 200
无输出内容。
#8 DeepSeek-v4-pro-04
成功
HTTP 200
无输出内容。
#9 DeepSeek-v4-pro-04
成功
HTTP 200
无输出内容。
#10 DeepSeek-v4-pro-02
成功
HTTP 200
无输出内容。
#11 DeepSeek-v4-pro-02
成功
HTTP 200
无输出内容。
#12 DeepSeek-v4-pro-02
成功
HTTP 200
无输出内容。
#13 jd-gemini-3.1-pro-preview
成功
HTTP 200
无输出内容。
#14 jd-gemini-3.1-pro-preview
成功
HTTP 200
无输出内容。
#15 jd-gemini-3.1-pro-preview
成功
HTTP 200
无输出内容。
#16 腾讯 Gemini 3.5 Flash
成功
HTTP 200
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue: Navigating the Nuances of Expert Communication**\n\nAlright, so the core of this request is for me to summarize a given text, but with a very specific constraint: it needs to be in the first person, as if these thoughts are *my* own. And not just a brief summary, but a \"fulsome\" one, detailing the *entire* thought process. The target audience is an \"expert in their field,\" which is a crucial cue. This means I don't need to over-explain basic concepts. Instead, I should lean into the intellectual engagement, the critical analysis, and the strategic decision-making that goes into formulating a response suitable for someone who already possesses a deep understanding of the subject matter.\n\nLet's break down what \"fulsome\" really means in this context. It's not just about length; it's about depth and thoroughness. It implies a comprehensive exploration of how I arrived at the final output. For an expert, this would involve:\n\n* **Deconstructing the Input:** First, I need to meticulously dissect the provided text. What are its main arguments? What is the author's under
#17 腾讯 Gemini 3.5 Flash
成功
HTTP 200
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue: Navigating the Nuances of Expert Communication**\n\nAlright, so the core of this request is for me to summarize a given text, but with a very specific constraint: it needs to be in the first person, as if these thoughts are *my* own. And not just a brief summary, but a \"fulsome\" one, detailing the *entire* thought process. The target audience is an \"expert in their field,\" which is a crucial cue. This means I don't need to over-explain basic concepts. Instead, I should lean into the intellectual engagement, the critical analysis, and the strategic decision-making that goes into formulating a response suitable for someone who already possesses a deep understanding of the subject matter.\n\nLet's break down what \"fulsome\" really means in this context. It's not just about length; it's about depth and thoroughness. It implies a comprehensive exploration of how I arrived at the final output. For an expert, this would involve:\n\n* **Deconstructing the Input:** First, I need to meticulously dissect the provided text. What are its main arguments? What is the author's under
#18 腾讯 Gemini 3.5 Flash
成功
HTTP 200
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue on Summarizing and the User's Expertise**\n\nAlright, let's break down this request. The core task is to summarize a piece of text, but the crucial constraints are:\n\n1. **First-Person Perspective:** I need to inhabit the *thoughts* described in the text, speaking as if they are my own internal musings. This isn't about me *reporting* on the thoughts; it's about me *having* them.\n2. **Fulsome Summary of Thought Process:** This means I can't just give a brief overview. I need to go deep into the *how* and *why* of the thinking, detailing the steps, the considerations, the nuances. It’s about laying bare the entire intellectual journey.\n3. **Target Audience is Expert:** The user is an expert. This implies I can skip over foundational explanations and assume a sophisticated understanding of the subject matter. I don't need to dumb anything down; in fact, I should probably use precise language and acknowledge the inherent complexities they'd expect.\n4. **Specific Starting Header:** The summary *must* begin with a bolded header, and the example given is \"My Summary:\". I
#19 qwen3.6-plus
成功
HTTP 200
{"status":"ok","message":"stable"}
#20 qwen3.6-plus
成功
HTTP 200
{"status":"ok","message":"stable"}
#21 pixflow-gemini-3.1-pro-preview
失败
HTTP 403
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#22 pixflow-gemini-3.1-pro-preview
失败
HTTP 403
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 pixflow-gemini-3.1-pro-preview
失败
HTTP 403
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#24 yuling-gpt-5.5
失败
HTTP 403
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#25 yuling-gpt-5.5
失败
HTTP 403
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#26 yuling-gpt-5.5
失败
HTTP 403
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#27 qwen3.6-plus
成功
HTTP 200
{"status":"ok","message":"stable"}
#28 Kimi K3 - Aliyun Bailian
成功
HTTP 200
无输出内容。
#29 Kimi K3 - Aliyun Bailian
成功
HTTP 200
无输出内容。
#30 Kimi K3 - Aliyun Bailian
成功
HTTP 200
无输出内容。
#31 Kimi K3
成功
HTTP 200
{"status":"ok","message":"stable"}
#32 Kimi K3
成功
HTTP 200
{"status":"ok","message":"stable"}
#33 Kimi K3
成功
HTTP 200
{"status":"ok","message":"stable"}
#34 Kimi K3 - TopenRouter
成功
HTTP 200
无输出内容。
#35 Kimi K3 - TopenRouter
成功
HTTP 200
无输出内容。
#36 Qwen3.8-Max
成功
HTTP 200
{"status":"ok","message":"stable"}
#37 Qwen3.8-Max
成功
HTTP 200
{"status":"ok","message":"stable"}
#38 Kimi K3 - TopenRouter
成功
HTTP 200
无输出内容。
#39 MiniMax H3 Context IR
失败
HTTP 400
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR
失败
HTTP 400
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 MiniMax H3 Context IR
失败
HTTP 400
HTTP 400: binding: expr_path=content, cause=missing required parameter
#42 Qwen3.8-Max
成功
HTTP 200
{"status":"ok","message":"stable"}
#43 yulin-gemini-3.7-flash-high
成功
HTTP 200
{"status":"ok","message":"stable"}
#44 yulin-gemini-3.7-flash-high
成功
HTTP 200
{"status":"ok","message":"stable"}
#45 yulin-gemini-3.7-flash-high
成功
HTTP 200
{"status":"ok","message":"stable"}
表格明细
| 渠道 | 状态 | 延迟 ms | HTTP | Tokens | 输出 / 错误 |
|---|---|---|---|---|---|
| DeepSeek-v4-pro-01 | 成功 | 689 | 200 | 113 | |
| DeepSeek-v4-pro-01 | 成功 | 1124 | 200 | 113 | |
| DeepSeek-v4-pro-01 | 成功 | 913 | 200 | 113 | |
| DeepSeek-v4-pro-03 | 成功 | 1133 | 200 | 113 | |
| DeepSeek-v4-pro-03 | 成功 | 1516 | 200 | 113 | |
| DeepSeek-v4-pro-03 | 成功 | 1149 | 200 | 113 | |
| DeepSeek-v4-pro-04 | 成功 | 1044 | 200 | 113 | |
| DeepSeek-v4-pro-04 | 成功 | 779 | 200 | 113 | |
| DeepSeek-v4-pro-04 | 成功 | 1135 | 200 | 113 | |
| DeepSeek-v4-pro-02 | 成功 | 1153 | 200 | 113 | |
| DeepSeek-v4-pro-02 | 成功 | 1076 | 200 | 113 | |
| DeepSeek-v4-pro-02 | 成功 | 1339 | 200 | 113 | |
| jd-gemini-3.1-pro-preview | 成功 | 2439 | 200 | 26 | |
| jd-gemini-3.1-pro-preview | 成功 | 2931 | 200 | 27 | |
| jd-gemini-3.1-pro-preview | 成功 | 3388 | 200 | 26 | |
| 腾讯 Gemini 3.5 Flash | 成功 | 4201 | 200 | 26 | {"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue: Navigating the Nuances of Expert Communication**\n\nAlright, so the core of this request is for me to summarize a given text, but with a very specific constraint: it needs to be in the first person, as if these thoughts are *my* own. And not just a brief summary, but a \"fulsome\" one, detailing the *entire* thought process. The target audience is an \"expert in their field,\" which is a crucial cue. This means I don't need to over-explain basic concepts. Instead, I should lean into the intellectual engagement, the critical analysis, and the strategic decision-making that goes into formulating a response suitable for someone who already possesses a deep understanding of the subject matter.\n\nLet's break down what \"fulsome\" really means in this context. It's not just about length; it's about depth and thoroughness. It implies a comprehensive exploration of how I arrived at the final output. For an expert, this would involve:\n\n* **Deconstructing the Input:** First, I need to meticulously dissect the provided text. What are its main arguments? What is the author's under |
| 腾讯 Gemini 3.5 Flash | 成功 | 4330 | 200 | 26 | {"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue: Navigating the Nuances of Expert Communication**\n\nAlright, so the core of this request is for me to summarize a given text, but with a very specific constraint: it needs to be in the first person, as if these thoughts are *my* own. And not just a brief summary, but a \"fulsome\" one, detailing the *entire* thought process. The target audience is an \"expert in their field,\" which is a crucial cue. This means I don't need to over-explain basic concepts. Instead, I should lean into the intellectual engagement, the critical analysis, and the strategic decision-making that goes into formulating a response suitable for someone who already possesses a deep understanding of the subject matter.\n\nLet's break down what \"fulsome\" really means in this context. It's not just about length; it's about depth and thoroughness. It implies a comprehensive exploration of how I arrived at the final output. For an expert, this would involve:\n\n* **Deconstructing the Input:** First, I need to meticulously dissect the provided text. What are its main arguments? What is the author's under |
| 腾讯 Gemini 3.5 Flash | 成功 | 5136 | 200 | 26 | {"index": 0, "message": {"role": "assistant", "content": null, "reasoning_content": "**My Internal Monologue on Summarizing and the User's Expertise**\n\nAlright, let's break down this request. The core task is to summarize a piece of text, but the crucial constraints are:\n\n1. **First-Person Perspective:** I need to inhabit the *thoughts* described in the text, speaking as if they are my own internal musings. This isn't about me *reporting* on the thoughts; it's about me *having* them.\n2. **Fulsome Summary of Thought Process:** This means I can't just give a brief overview. I need to go deep into the *how* and *why* of the thinking, detailing the steps, the considerations, the nuances. It’s about laying bare the entire intellectual journey.\n3. **Target Audience is Expert:** The user is an expert. This implies I can skip over foundational explanations and assume a sophisticated understanding of the subject matter. I don't need to dumb anything down; in fact, I should probably use precise language and acknowledge the inherent complexities they'd expect.\n4. **Specific Starting Header:** The summary *must* begin with a bolded header, and the example given is \"My Summary:\". I |
| qwen3.6-plus | 成功 | 5912 | 200 | 331 | {"status":"ok","message":"stable"} |
| qwen3.6-plus | 成功 | 5191 | 200 | 282 | {"status":"ok","message":"stable"} |
| pixflow-gemini-3.1-pro-preview | 失败 | 531 | 403 | - | HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"} |
| pixflow-gemini-3.1-pro-preview | 失败 | 466 | 403 | - | HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"} |
| pixflow-gemini-3.1-pro-preview | 失败 | 497 | 403 | - | HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"} |
| yuling-gpt-5.5 | 失败 | 478 | 403 | - | HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"} |
| yuling-gpt-5.5 | 失败 | 525 | 403 | - | HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"} |
| yuling-gpt-5.5 | 失败 | 513 | 403 | - | HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"} |
| qwen3.6-plus | 成功 | 5982 | 200 | 346 | {"status":"ok","message":"stable"} |
| Kimi K3 - Aliyun Bailian | 成功 | 1966 | 200 | 115 | |
| Kimi K3 - Aliyun Bailian | 成功 | 2955 | 200 | 115 | |
| Kimi K3 - Aliyun Bailian | 成功 | 2481 | 200 | 115 | |
| Kimi K3 | 成功 | 6176 | 200 | 202 | {"status":"ok","message":"stable"} |
| Kimi K3 | 成功 | 8270 | 200 | 207 | {"status":"ok","message":"stable"} |
| Kimi K3 | 成功 | 8278 | 200 | 237 | {"status":"ok","message":"stable"} |
| Kimi K3 - TopenRouter | 成功 | 2795 | 200 | 116 | |
| Kimi K3 - TopenRouter | 成功 | 3838 | 200 | 116 | |
| Qwen3.8-Max | 成功 | 1872 | 200 | 131 | {"status":"ok","message":"stable"} |
| Qwen3.8-Max | 成功 | 2229 | 200 | 136 | {"status":"ok","message":"stable"} |
| Kimi K3 - TopenRouter | 成功 | 18316 | 200 | 116 | |
| MiniMax H3 Context IR | 失败 | 154 | 400 | - | HTTP 400: binding: expr_path=content, cause=missing required parameter |
| MiniMax H3 Context IR | 失败 | 175 | 400 | - | HTTP 400: binding: expr_path=content, cause=missing required parameter |
| MiniMax H3 Context IR | 失败 | 156 | 400 | - | HTTP 400: binding: expr_path=content, cause=missing required parameter |
| Qwen3.8-Max | 成功 | 1728 | 200 | 130 | {"status":"ok","message":"stable"} |
| yulin-gemini-3.7-flash-high | 成功 | 5280 | 200 | 143 | {"status":"ok","message":"stable"} |
| yulin-gemini-3.7-flash-high | 成功 | 5907 | 200 | 186 | {"status":"ok","message":"stable"} |
| yulin-gemini-3.7-flash-high | 成功 | 4682 | 200 | 173 | {"status":"ok","message":"stable"} |