历史详情

Run ID: 20260830-045553-384052cf

返回历史

测试结果

Run ID: 20260830-045553-384052cf

导出 JSON
总请求45
成功 / 失败36/9
成功率80.0%
平均延迟2723 ms
P95 / Tokens5241 / 4456
渠道模型成功失败成功率失败率稳定性平均延迟 msP95 msTokens首个错误
DeepSeek-v4-pro-02 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 839 1029 339
DeepSeek-v4-pro-04 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 937 1189 339
DeepSeek-v4-pro-01 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1028 1133 339
DeepSeek-v4-pro-03 deepseek-v4-pro 3/3 0/3 100.0% 0.0% 稳定 1197 1383 339
Kimi K3 - TopenRouter kimi-k3 3/3 0/3 100.0% 0.0% 稳定 1973 2435 459
Qwen3.8-Max qwen3.8-max 3/3 0/3 100.0% 0.0% 稳定 2535 2720 383
jd-gemini-3.1-pro-preview gemini-3.1-pro-preview 3/3 0/3 100.0% 0.0% 稳定 2603 3101 81
Kimi K3 - Aliyun Bailian kimi/kimi-k3 3/3 0/3 100.0% 0.0% 稳定 2995 3350 345
Kimi K3 kimi-k3 3/3 0/3 100.0% 0.0% 稳定 4047 4712 345
yulin-gemini-3.7-flash-high gemini-3.7-flash-high 3/3 0/3 100.0% 0.0% 稳定 4268 4575 537
腾讯 Gemini 3.5 Flash gemini-3.5-flash 3/3 0/3 100.0% 0.0% 可用 4988 5444 78
qwen3.6-plus qwen3.6-plus 3/3 0/3 100.0% 0.0% 可用 5268 6418 872
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 延迟:960 ms Tokens:113 时间:2026-08-30 04:55:01
JSON
无输出内容。
#2 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:991 ms Tokens:113 时间:2026-08-30 04:55:01
JSON
无输出内容。
#3 DeepSeek-v4-pro-01 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1133 ms Tokens:113 时间:2026-08-30 04:55:02
JSON
无输出内容。
#4 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1383 ms Tokens:113 时间:2026-08-30 04:55:02
JSON
无输出内容。
#5 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1056 ms Tokens:113 时间:2026-08-30 04:55:03
JSON
无输出内容。
#6 DeepSeek-v4-pro-03 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1152 ms Tokens:113 时间:2026-08-30 04:55:03
JSON
无输出内容。
#7 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1189 ms Tokens:113 时间:2026-08-30 04:55:04
JSON
无输出内容。
#8 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:870 ms Tokens:113 时间:2026-08-30 04:55:05
JSON
无输出内容。
#9 DeepSeek-v4-pro-04 成功 HTTP 200
模型:deepseek-v4-pro 延迟:754 ms Tokens:113 时间:2026-08-30 04:55:05
JSON
无输出内容。
#10 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:722 ms Tokens:113 时间:2026-08-30 04:55:05
JSON
无输出内容。
#11 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:766 ms Tokens:113 时间:2026-08-30 04:55:06
JSON
无输出内容。
#12 DeepSeek-v4-pro-02 成功 HTTP 200
模型:deepseek-v4-pro 延迟:1029 ms Tokens:113 时间:2026-08-30 04:55:06
JSON
无输出内容。
#13 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2006 ms Tokens:27 时间:2026-08-30 04:55:07
JSON
无输出内容。
#14 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:2702 ms Tokens:27 时间:2026-08-30 04:55:07
JSON
无输出内容。
#15 jd-gemini-3.1-pro-preview 成功 HTTP 200
模型:gemini-3.1-pro-preview 延迟:3101 ms Tokens:27 时间:2026-08-30 04:55:09
JSON
无输出内容。
#16 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:4281 ms Tokens:26 时间:2026-08-30 04:55:10
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 延迟:5444 ms Tokens:26 时间:2026-08-30 04:55:12
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 腾讯 Gemini 3.5 Flash 成功 HTTP 200
模型:gemini-3.5-flash 延迟:5241 ms Tokens:26 时间:2026-08-30 04:55:14
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
#19 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:5134 ms Tokens:292 时间:2026-08-30 04:55:18
JSON
{"status":"ok","message":"stable"}
#20 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:4253 ms Tokens:239 时间:2026-08-30 04:55:19
JSON
{"status":"ok","message":"stable"}
#21 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:541 ms Tokens:- 时间:2026-08-30 04:55:23
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#22 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:535 ms Tokens:- 时间:2026-08-30 04:55:24
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#23 pixflow-gemini-3.1-pro-preview 失败 HTTP 403
模型:gemini-3.1-pro-preview 延迟:510 ms Tokens:- 时间:2026-08-30 04:55:25
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#24 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:492 ms Tokens:- 时间:2026-08-30 04:55:25
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#25 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:477 ms Tokens:- 时间:2026-08-30 04:55:26
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#26 yuling-gpt-5.5 失败 HTTP 403
模型:gpt-5.5 延迟:460 ms Tokens:- 时间:2026-08-30 04:55:26
JSON
HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
#27 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2642 ms Tokens:115 时间:2026-08-30 04:55:26
JSON
无输出内容。
#28 qwen3.6-plus 成功 HTTP 200
模型:qwen3.6-plus 延迟:6418 ms Tokens:341 时间:2026-08-30 04:55:23
JSON
{"status":"ok","message":"stable"}
#29 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:2995 ms Tokens:115 时间:2026-08-30 04:55:29
JSON
无输出内容。
#30 Kimi K3 - Aliyun Bailian 成功 HTTP 200
模型:kimi/kimi-k3 延迟:3350 ms Tokens:115 时间:2026-08-30 04:55:29
JSON
无输出内容。
#31 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:3817 ms Tokens:115 时间:2026-08-30 04:55:33
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to respond with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
#32 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:4712 ms Tokens:115 时间:2026-08-30 04:55:32
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only a specific JSON:"}, "logprobs": null, "finish_reason": "length"}
#33 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:2189 ms Tokens:153 时间:2026-08-30 04:55:37
JSON
无输出内容。
#34 Kimi K3 成功 HTTP 200
模型:kimi-k3 延迟:3614 ms Tokens:115 时间:2026-08-30 04:55:37
JSON
{"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to respond with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
#35 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:1295 ms Tokens:153 时间:2026-08-30 04:55:40
JSON
无输出内容。
#36 Kimi K3 - TopenRouter 成功 HTTP 200
模型:kimi-k3 延迟:2435 ms Tokens:153 时间:2026-08-30 04:55:39
JSON
无输出内容。
#37 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2312 ms Tokens:125 时间:2026-08-30 04:55:41
JSON
{"status":"ok","message":"stable"}
#38 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2720 ms Tokens:129 时间:2026-08-30 04:55:41
JSON
{"status":"ok","message":"stable"}
#39 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:196 ms Tokens:- 时间:2026-08-30 04:55:44
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#40 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:189 ms Tokens:- 时间:2026-08-30 04:55:44
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#41 MiniMax H3 Context IR 失败 HTTP 400
模型:MiniMax-H3 延迟:201 ms Tokens:- 时间:2026-08-30 04:55:45
JSON
HTTP 400: binding: expr_path=content, cause=missing required parameter
#42 Qwen3.8-Max 成功 HTTP 200
模型:qwen3.8-max 延迟:2574 ms Tokens:129 时间:2026-08-30 04:55:44
JSON
{"status":"ok","message":"stable"}
#43 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4575 ms Tokens:176 时间:2026-08-30 04:55:45
JSON
{"status":"ok","message":"stable"}
#44 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4209 ms Tokens:174 时间:2026-08-30 04:55:46
JSON
{"status":"ok","message":"stable"}
#45 yulin-gemini-3.7-flash-high 成功 HTTP 200
模型:gemini-3.7-flash-high 延迟:4021 ms Tokens:187 时间:2026-08-30 04:55:49
JSON
{"status":"ok","message":"stable"}

表格明细

渠道状态延迟 msHTTPTokens输出 / 错误
DeepSeek-v4-pro-01 成功 960 200 113
DeepSeek-v4-pro-01 成功 991 200 113
DeepSeek-v4-pro-01 成功 1133 200 113
DeepSeek-v4-pro-03 成功 1383 200 113
DeepSeek-v4-pro-03 成功 1056 200 113
DeepSeek-v4-pro-03 成功 1152 200 113
DeepSeek-v4-pro-04 成功 1189 200 113
DeepSeek-v4-pro-04 成功 870 200 113
DeepSeek-v4-pro-04 成功 754 200 113
DeepSeek-v4-pro-02 成功 722 200 113
DeepSeek-v4-pro-02 成功 766 200 113
DeepSeek-v4-pro-02 成功 1029 200 113
jd-gemini-3.1-pro-preview 成功 2006 200 27
jd-gemini-3.1-pro-preview 成功 2702 200 27
jd-gemini-3.1-pro-preview 成功 3101 200 27
腾讯 Gemini 3.5 Flash 成功 4281 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 成功 5444 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 成功 5241 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 成功 5134 200 292 {"status":"ok","message":"stable"}
qwen3.6-plus 成功 4253 200 239 {"status":"ok","message":"stable"}
pixflow-gemini-3.1-pro-preview 失败 541 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 535 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
pixflow-gemini-3.1-pro-preview 失败 510 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 492 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 477 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
yuling-gpt-5.5 失败 460 403 - HTTP 403: {"code":"INSUFFICIENT_BALANCE","message":"Insufficient account balance"}
Kimi K3 - Aliyun Bailian 成功 2642 200 115
qwen3.6-plus 成功 6418 200 341 {"status":"ok","message":"stable"}
Kimi K3 - Aliyun Bailian 成功 2995 200 115
Kimi K3 - Aliyun Bailian 成功 3350 200 115
Kimi K3 成功 3817 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to respond with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 成功 4712 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to reply with only a specific JSON:"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 - TopenRouter 成功 2189 200 153
Kimi K3 成功 3614 200 115 {"index": 0, "message": {"role": "assistant", "content": null, "reasoning": "The user is asking me to respond with only JSON: {\"status"}, "logprobs": null, "finish_reason": "length"}
Kimi K3 - TopenRouter 成功 1295 200 153
Kimi K3 - TopenRouter 成功 2435 200 153
Qwen3.8-Max 成功 2312 200 125 {"status":"ok","message":"stable"}
Qwen3.8-Max 成功 2720 200 129 {"status":"ok","message":"stable"}
MiniMax H3 Context IR 失败 196 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 189 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
MiniMax H3 Context IR 失败 201 400 - HTTP 400: binding: expr_path=content, cause=missing required parameter
Qwen3.8-Max 成功 2574 200 129 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4575 200 176 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4209 200 174 {"status":"ok","message":"stable"}
yulin-gemini-3.7-flash-high 成功 4021 200 187 {"status":"ok","message":"stable"}