历史详情

Run ID: 20260828-141334-73706f01

返回历史

测试结果

Run ID: 20260828-141334-73706f01

导出 JSON
总请求45
成功 / 失败35/10
成功率77.78%
平均延迟4303 ms
P95 / Tokens10434 / 4418
渠道模型成功失败成功率失败率稳定性平均延迟 msP95 msTokens首个错误
DeepSeek-v4-pro-04 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1175 1389 339
DeepSeek-v4-pro-01 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1183 1625 339
DeepSeek-v4-pro-02 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1488 1577 339
DeepSeek-v4-pro-03 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1511 1686 339
Kimi K3 - Aliyun Bailian kimi/kimi-k3 3/3 0/3 100.0% 0.0% 稳定 2215 2304 345
Qwen3.8-Max qwen3.8-max 3/3 0/3 100.0% 0.0% 稳定 2961 3644 403
yulin-gemini-3.7-flash-high gemini-3.7-flash-high 3/3 0/3 100.0% 0.0% 可用 4534 5098 524
腾讯 Gemini 3.5 Flash gemini-3.5-flash 3/3 0/3 100.0% 0.0% 可用 5001 5607 78
qwen3.6-plus qwen3.6-plus 3/3 0/3 100.0% 0.0% 可用 5305 6017 914
Kimi K3 kimi-k3 3/3 0/3 100.0% 0.0% 可用 8360 10574 345
Kimi K3 - TopenRouter kimi-k3 3/3 0/3 100.0% 0.0% 可用 14699 23820 401
jd-gemini-3.1-pro-preview gemini-3.1-pro-preview 2/3 1/3 66.67% 33.33% 不稳定 2657 3203 52 timeout: The read operation timed out
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
模型:deepseek-v4-pro 延迟:942 ms Tokens:113 时间:2026-08-28 14:12:00
JSON
无输出内容。
#2 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:984 ms Tokens:113 时间:2026-08-28 14:12:00
JSON
无输出内容。
#3 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1625 ms Tokens:113 时间:2026-08-28 14:12:01
JSON
无输出内容。
#4 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1686 ms Tokens:113 时间:2026-08-28 14:12:01
JSON
无输出内容。
#5 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1240 ms Tokens:113 时间:2026-08-28 14:12:02
JSON
无输出内容。
#6 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1608 ms Tokens:113 时间:2026-08-28 14:12:02
JSON
无输出内容。
#7 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1389 ms Tokens:113 时间:2026-08-28 14:12:03
JSON
无输出内容。
#8 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1235 ms Tokens:113 时间:2026-08-28 14:12:04
JSON
无输出内容。
#9 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:903 ms Tokens:113 时间:2026-08-28 14:12:05
JSON
无输出内容。
#10 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1474 ms Tokens:113 时间:2026-08-28 14:12:05
JSON
无输出内容。
#11 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1577 ms Tokens:113 时间:2026-08-28 14:12:06
JSON
无输出内容。
#12 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1414 ms Tokens:113 时间:2026-08-28 14:12:07
JSON
无输出内容。
#13 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:3203 ms Tokens:26 时间:2026-08-28 14:12:08
JSON
无输出内容。
#14 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2111 ms Tokens:26 时间:2026-08-28 14:12:11
JSON
无输出内容。
#15 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:5607 ms Tokens:26 时间:2026-08-28 14:12:13
JSON
{"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
#16 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4339 ms Tokens:26 时间:2026-08-28 14:12:19
JSON
{"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
模型:gemini-3.5-flash 延迟:5058 ms Tokens:26 时间:2026-08-28 14:12:23
JSON
{"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
#18 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:6017 ms Tokens:346 时间:2026-08-28 14:12:28
JSON
{"status":"ok","message":"stable"}
#19 jd-gemini-3.1-pro-preview 失败 HTTP -
模型:gemini-3.1-pro-preview 延迟:30250 ms Tokens:- 时间:2026-08-28 14:12:07
JSON
timeout: The read operation timed out
#20 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:4031 ms Tokens:230 时间:2026-08-28 14:12:34
JSON
```json {"status":"ok","message":"stable"} ```
#21 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:535 ms Tokens:- 时间:2026-08-28 14:12:38
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#22 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:524 ms Tokens:- 时间:2026-08-28 14:12:39
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:526 ms Tokens:- 时间:2026-08-28 14:12:39
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#24 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:485 ms Tokens:- 时间:2026-08-28 14:12:40
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#25 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:467 ms Tokens:- 时间:2026-08-28 14:12:40
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#26 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:512 ms Tokens:- 时间:2026-08-28 14:12:41
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#27 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:5868 ms Tokens:338 时间:2026-08-28 14:12:38
JSON
{"status":"ok","message":"stable"}
#28 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2304 ms Tokens:115 时间:2026-08-28 14:12:41
JSON
无输出内容。
#29 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2246 ms Tokens:115 时间:2026-08-28 14:12:43
JSON
无输出内容。
#30 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2096 ms Tokens:115 时间:2026-08-28 14:12:44
JSON
无输出内容。
#31 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:9963 ms Tokens:115 时间:2026-08-28 14:12:46
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
#32 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:10574 ms Tokens:115 时间:2026-08-28 14:12:46
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
#33 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4543 ms Tokens:115 时间:2026-08-28 14:12:56
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
#34 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:9843 ms Tokens:116 时间:2026-08-28 14:12:56
JSON
无输出内容。
#35 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:10434 ms Tokens:169 时间:2026-08-28 14:13:00
JSON
{"status":"ok","message":"stable"}
#36 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2266 ms Tokens:125 时间:2026-08-28 14:13:11
JSON
{"status":"ok","message":"stable"}
#37 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2974 ms Tokens:137 时间:2026-08-28 14:13:13
JSON
{"status":"ok","message":"stable"}
#38 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:3644 ms Tokens:141 时间:2026-08-28 14:13:16
JSON
{"status":"ok","message":"stable"}
#39 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:153 ms Tokens:- 时间:2026-08-28 14:13:20
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:168 ms Tokens:- 时间:2026-08-28 14:13:20
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:190 ms Tokens:- 时间:2026-08-28 14:13:20
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#42 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:5098 ms Tokens:176 时间:2026-08-28 14:13:20
JSON
{"status":"ok","message":"stable"}
#43 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4134 ms Tokens:163 时间:2026-08-28 14:13:25
JSON
{"status":"ok","message":"stable"}
#44 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:23820 ms Tokens:116 时间:2026-08-28 14:13:06
JSON
无输出内容。
#45 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4370 ms Tokens:185 时间:2026-08-28 14:13:29
JSON
{"status":"ok","message":"stable"}

表格明细

渠道状态延迟 msHTTPTokens输出 / 错误
DeepSeek-v4-pro-01 成功 942 200 113
DeepSeek-v4-pro-01 成功 984 200 113
DeepSeek-v4-pro-01 成功 1625 200 113
DeepSeek-v4-pro-03 成功 1686 200 113
DeepSeek-v4-pro-03 成功 1240 200 113
DeepSeek-v4-pro-03 成功 1608 200 113
DeepSeek-v4-pro-04 成功 1389 200 113
DeepSeek-v4-pro-04 成功 1235 200 113
DeepSeek-v4-pro-04 成功 903 200 113
DeepSeek-v4-pro-02 成功 1474 200 113
DeepSeek-v4-pro-02 成功 1577 200 113
DeepSeek-v4-pro-02 成功 1414 200 113
jd-gemini-3.1-pro-preview 成功 3203 200 26
jd-gemini-3.1-pro-preview 成功 2111 200 26
腾讯 Gemini 3.5 Flash 成功 5607 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
腾讯 Gemini 3.5 Flash 成功 4339 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 成功 5058 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 成功 6017 200 346 {"status":"ok","message":"stable"}
jd-gemini-3.1-pro-preview 失败 30250 - - timeout: The read operation timed out
qwen3.6-plus 成功 4031 200 230 ```json {"status":"ok","message":"stable"} ```
pixflow-gemini-3.1-pro-preview 失败 535 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 524 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 526 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 485 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 467 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 512 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
qwen3.6-plus 成功 5868 200 338 {"status":"ok","message":"stable"}
Kimi K3 - Aliyun Bailian 成功 2304 200 115
Kimi K3 - Aliyun Bailian 成功 2246 200 115
Kimi K3 - Aliyun Bailian 成功 2096 200 115
Kimi K3 成功 9963 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 10574 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 4543 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 - TopenRouter 成功 9843 200 116
Kimi K3 - TopenRouter 成功 10434 200 169 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 2266 200 125 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 2974 200 137 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 3644 200 141 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 153 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 168 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 190 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
yulin-gemini-3.7-flash-high 成功 5098 200 176 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4134 200 163 {"status":"ok","message":"stable"}
Kimi K3 - TopenRouter 成功 23820 200 116
yulin-gemini-3.7-flash-high 成功 4370 200 185 {"status":"ok","message":"stable"}