历史详情

Run ID: 20260827-073049-f7a1ac31

返回历史

测试结果

Run ID: 20260827-073049-f7a1ac31

导出 JSON
总请求45
成功 / 失败36/9
成功率80.0%
平均延迟2745 ms
P95 / Tokens4806 / 4108
渠道模型成功失败成功率失败率稳定性平均延迟 msP95 msTokens首个错误
DeepSeek-v4-pro-01 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1109 1270 339
DeepSeek-v4-pro-03 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1268 1319 339
DeepSeek-v4-pro-04 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1514 1549 339
DeepSeek-v4-pro-02 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1712 1973 339
Qwen3.8-Max qwen3.8-max 3/3 0/3 100.0% 0.0% 稳定 2088 2312 389
jd-gemini-3.1-pro-preview gemini-3.1-pro-preview 3/3 0/3 100.0% 0.0% 稳定 2367 2526 78
Kimi K3 - Aliyun Bailian kimi/kimi-k3 3/3 0/3 100.0% 0.0% 稳定 2742 3300 345
Kimi K3 - TopenRouter kimi-k3 3/3 0/3 100.0% 0.0% 稳定 3122 4001 348
Kimi K3 kimi-k3 3/3 0/3 100.0% 0.0% 稳定 3909 4096 345
qwen3.6-plus qwen3.6-plus 3/3 0/3 100.0% 0.0% 稳定 3937 4806 674
腾讯 Gemini 3.5 Flash gemini-3.5-flash 3/3 0/3 100.0% 0.0% 可用 4532 5033 78
yulin-gemini-3.7-flash-high gemini-3.7-flash-high 3/3 0/3 100.0% 0.0% 稳定 4644 4978 495
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 延迟:1137 ms Tokens:113 时间:2026-08-27 07:29:55
JSON
无输出内容。
#2 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1270 ms Tokens:113 时间:2026-08-27 07:29:55
JSON
无输出内容。
#3 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:921 ms Tokens:113 时间:2026-08-27 07:29:57
JSON
无输出内容。
#4 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1319 ms Tokens:113 时间:2026-08-27 07:29:57
JSON
无输出内容。
#5 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1301 ms Tokens:113 时间:2026-08-27 07:29:57
JSON
无输出内容。
#6 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1184 ms Tokens:113 时间:2026-08-27 07:29:58
JSON
无输出内容。
#7 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1549 ms Tokens:113 时间:2026-08-27 07:29:59
JSON
无输出内容。
#8 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1533 ms Tokens:113 时间:2026-08-27 07:29:59
JSON
无输出内容。
#9 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1462 ms Tokens:113 时间:2026-08-27 07:30:00
JSON
无输出内容。
#10 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1439 ms Tokens:113 时间:2026-08-27 07:30:01
JSON
无输出内容。
#11 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1724 ms Tokens:113 时间:2026-08-27 07:30:02
JSON
{"
#12 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1973 ms Tokens:113 时间:2026-08-27 07:30:02
JSON
无输出内容。
#13 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2526 ms Tokens:26 时间:2026-08-27 07:30:03
JSON
无输出内容。
#14 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2416 ms Tokens:26 时间:2026-08-27 07:30:04
JSON
无输出内容。
#15 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2159 ms Tokens:26 时间:2026-08-27 07:30:06
JSON
无输出内容。
#16 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:5033 ms Tokens:26 时间:2026-08-27 07:30:07
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
#17 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4371 ms Tokens:26 时间:2026-08-27 07:30:08
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
#18 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4194 ms Tokens:26 时间:2026-08-27 07:30:12
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
#19 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:4806 ms Tokens:268 时间:2026-08-27 07:30:13
JSON
{"status":"ok","message":"stable"}
#20 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:3595 ms Tokens:209 时间:2026-08-27 07:30:16
JSON
{"status":"ok","message":"stable"}
#21 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:536 ms Tokens:- 时间:2026-08-27 07:30:19
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#22 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:530 ms Tokens:- 时间:2026-08-27 07:30:20
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:3412 ms Tokens:197 时间:2026-08-27 07:30:17
JSON
{"status":"ok","message":"stable"}
#24 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:515 ms Tokens:- 时间:2026-08-27 07:30:20
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#25 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:480 ms Tokens:- 时间:2026-08-27 07:30:21
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#26 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:483 ms Tokens:- 时间:2026-08-27 07:30:21
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#27 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:501 ms Tokens:- 时间:2026-08-27 07:30:21
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#28 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2756 ms Tokens:115 时间:2026-08-27 07:30:22
JSON
无输出内容。
#29 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:3300 ms Tokens:115 时间:2026-08-27 07:30:21
JSON
无输出内容。
#30 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2172 ms Tokens:115 时间:2026-08-27 07:30:24
JSON
无输出内容。
#31 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:3718 ms Tokens:115 时间:2026-08-27 07:30:25
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "We need respond to user in Chinese: \"请只回复 JSON:{\"status"}, "logprobs": null, "finish_reason": "length"}
#32 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:3913 ms Tokens:115 时间:2026-08-27 07:30:27
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "We need answer user in Chinese asks: \"请只回复 JSON:{\"status"}, "logprobs": null, "finish_reason": "length"}
#33 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4096 ms Tokens:115 时间:2026-08-27 07:30:28
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status\":\"ok\",\""}, "logprobs": null, "finish_reason": "length"}
#34 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:4001 ms Tokens:116 时间:2026-08-27 07:30:31
JSON
无输出内容。
#35 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:2312 ms Tokens:116 时间:2026-08-27 07:30:33
JSON
无输出内容。
#36 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:1859 ms Tokens:128 时间:2026-08-27 07:30:35
JSON
{"status":"ok","message":"stable"}
#37 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:3054 ms Tokens:116 时间:2026-08-27 07:30:35
JSON
无输出内容。
#38 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2312 ms Tokens:125 时间:2026-08-27 07:30:37
JSON
{"status":"ok","message":"stable"}
#39 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:196 ms Tokens:- 时间:2026-08-27 07:30:39
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:194 ms Tokens:- 时间:2026-08-27 07:30:39
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:199 ms Tokens:- 时间:2026-08-27 07:30:39
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#42 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2093 ms Tokens:136 时间:2026-08-27 07:30:38
JSON
{"status":"ok","message":"stable"}
#43 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4656 ms Tokens:149 时间:2026-08-27 07:30:40
JSON
{"status":"ok","message":"stable"}
#44 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4978 ms Tokens:185 时间:2026-08-27 07:30:40
JSON
{"status":"ok","message":"stable"}
#45 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4298 ms Tokens:161 时间:2026-08-27 07:30:44
JSON
{"status":"ok","message":"stable"}

表格明细

渠道状态延迟 msHTTPTokens输出 / 错误
DeepSeek-v4-pro-01 成功 1137 200 113
DeepSeek-v4-pro-01 成功 1270 200 113
DeepSeek-v4-pro-01 成功 921 200 113
DeepSeek-v4-pro-03 成功 1319 200 113
DeepSeek-v4-pro-03 成功 1301 200 113
DeepSeek-v4-pro-03 成功 1184 200 113
DeepSeek-v4-pro-04 成功 1549 200 113
DeepSeek-v4-pro-04 成功 1533 200 113
DeepSeek-v4-pro-04 成功 1462 200 113
DeepSeek-v4-pro-02 成功 1439 200 113
DeepSeek-v4-pro-02 成功 1724 200 113 {"
DeepSeek-v4-pro-02 成功 1973 200 113
jd-gemini-3.1-pro-preview 成功 2526 200 26
jd-gemini-3.1-pro-preview 成功 2416 200 26
jd-gemini-3.1-pro-preview 成功 2159 200 26
腾讯 Gemini 3.5 Flash 成功 5033 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 成功 4371 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 成功 4194 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
qwen3.6-plus 成功 4806 200 268 {"status":"ok","message":"stable"}
qwen3.6-plus 成功 3595 200 209 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 536 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 530 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
qwen3.6-plus 成功 3412 200 197 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 515 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 480 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 483 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 501 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
Kimi K3 - Aliyun Bailian 成功 2756 200 115
Kimi K3 - Aliyun Bailian 成功 3300 200 115
Kimi K3 - Aliyun Bailian 成功 2172 200 115
Kimi K3 成功 3718 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "We need respond to user in Chinese: \"请只回复 JSON:{\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 3913 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "We need answer user in Chinese asks: \"请只回复 JSON:{\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 4096 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only JSON: {\"status\":\"ok\",\""}, "logprobs": null, "finish_reason": "length"}
Kimi K3 - TopenRouter 成功 4001 200 116
Kimi K3 - TopenRouter 成功 2312 200 116
Qwen3.8-Max 成功 1859 200 128 {"status":"ok","message":"stable"}
Kimi K3 - TopenRouter 成功 3054 200 116
Qwen3.8-Max 成功 2312 200 125 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 196 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 194 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 199 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
Qwen3.8-Max 成功 2093 200 136 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4656 200 149 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4978 200 185 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4298 200 161 {"status":"ok","message":"stable"}